< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate] Session handle lifecycle question


You can override the AppDialogSet or AppDialog destructor to cleanup your map.  The AppDialogSet and AppDialog go away when the session does (assuming there are no outstanding notify subscriptions, from refers).

 

 

 

From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Kovar, William (Bill)
Sent: Friday, October 13, 2006 5:30 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] Session handle lifecycle question

 

All,

 

Is there a way to know when a session has been 'disconnected' from its handle, i.e. handle.isValid() == false other then to check for it??

 

I stash session handles within my call management logic and had hoped that I can remove them in onTerminated() but the handle is still valid and isTerminated() = true. Is there somewhere in the destructor of either AppDialog or AppDialogSet that I can look to find out if the session is no longer valid? This way I can clean my calls that this session is a part of.

 

Thanks

 

Bill Kovar