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

Re: [reSIProcate] re-entrant behaviour


That was the intent.  I don't know of any issues with calling anything.
If you find something that doesn't work, then we should fix it or
document it.  

Scott

> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx
> [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of
> Daniel Pocock
> Sent: Monday, February 12, 2007 4:49 AM
> To: resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
> Subject: [reSIProcate] re-entrant behaviour
> 
> 
> 
> When an application derives from a class such as InviteSessionHandler,
> and receives callbacks from the stack, are there any limitations or
> recommendations on making calls to the stack while in the callback
> handler?  E.g. is it safe to call all of the methods of
> DialogUsageManager and/or (Client/Server)InviteSession, while
> processing
> InviteSessionHandler::onConnected(), for instance?
> 
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel