| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index | Next in Thread > |
|
AppDialog::getInviteSession() From: Kovar, William (Bill) [mailto:bkovar@xxxxxxxxx] Sent: Mon 10/16/2006 6:18 PM To: Scott Godin; resiprocate-devel@xxxxxxxxxxxxxxxxxxx Subject: RE: [reSIProcate] Session handle lifecycle question Scott,
Yes I know about the destruction part, but I can't seem to figure out how to get to the session. Can you enlighten me as to the method call to be used in the destructor of AppDialog to get the session handle (or session)? From: Scott Godin [mailto:slgodin@xxxxxxxxxxxx] Sent: Friday, October 13, 2006 7:52 PM To: Kovar, William (Bill); resiprocate-devel@xxxxxxxxxxxxxxxxxxx Subject: 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)
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 |