Re: [reSIProcate] Best way to handle ServerSubscriptions?

["Scott Godin" <slgodin@xxxxxxxxxxxx>]

I use method 1 frequently – it offers good flexibility without needing to modify DUM.

 

Note:  There is also an applyToAllServerSubscriptions function in DUM that you may find useful.  But it will involve an iteration across all subscriptions to find the ones you want.

 

From: resiprocate-devel-bounces@xxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxx] On Behalf Of Matthias Moetje
Sent: Monday, October 08, 2007 9:17 AM
To: resiprocate-devel
Subject: [reSIProcate] Best way to handle ServerSubscriptions?

 

Hi,

 

I am currently trying to find the best way to track and update ServerSubscriptions. In order to perform updates I need to be able to find all subscriptions which are matching a certain key (AOR).

I am thinking about the following two concepts:

 

1.       Keep my own map of ServerSubscriptions. Add to the map on createAppDialogSet and remove from the map when the dialogset is destroyed

2.       Rely on the list that is kept by dum (mServerSubscriptions) and use mDum.mServerSubscriptions.equal_range(key) to retrieve all subscriptions matching a certain AOR

 

The problem with 1 is that it creates additional overhead. The problem with 2 is that mServerSubscriptions is a private member of DialogUsageManager. There is a function findServerSubscription but is takes a DialogId as a parameter, so this doesn’t help much.

 

What should I do? Should I add a function  findServerSubscriptions(Data key) to DialogUsageManager?

 

 

Best regards,

Freundliche Grüße,

 

Matthias Moetje

TERASENS GmbH
Augustenstraße 24
80333 Munich
GERMANY

 

Phone: Fax: e-mail: Web:

+49.89.143370-0 +49.89.143370-22 info@xxxxxxxxxxxx www.terasens.com