With the current TU routing, it is only possible to direct
SUBSCRIBE request to either the proxy TU or DUM TU (ServerSubscriptionHandler)
based on the Event Type. However it would be possible to build your own
custom MessageFilterRule to do what you want. Check out repro.cxx to see
how the message filter rule list is currently generated (setMessageFilterRuleList), and
MessageFilterRule.hxx/cxx.
Scott
From:
repro-devel-bounces@xxxxxxxxxxxxxxx
[mailto:repro-devel-bounces@xxxxxxxxxxxxxxx] On Behalf Of pauldarl@xxxxxxxxx
Sent: Tuesday, November 18, 2008 2:11 PM
To: repro-devel@xxxxxxxxxxxxxxx
Subject: [repro-devel] Proxying SUBSCRIBE requests
Hi,
Does repro support proxying SUBSCRIBE requests that it determine to be for an
event to be handled by another server (eg. presence for a remote presentity),
while handling other SUBSCRIBE requests for the event locally, eg. the presence
of a local user?
I've added a server subscription handler to DUM for the presence event. This
causes a match for all subscriptions to this event, regardless of whether the
local server can act as the presentity for the subscription. There seems no way
to skip handling of SUBSCRIBE requests (so that the proxy can process them),
other than to not handle any events of the type.
I was thinking that my handler could generate a client subscription to the the
remote presence server, and treat received NOTIFY requests from this server as
a publish, thus generating new NOTIFY requests to the original subscriber. But
it seems this should not be necessary, and proxying the SUBSCRIBE is the
correct behavior.
thanks
Paul