RE: [reSIProcate] clean shutdown
You should call DialogUsageManager::shutdown(), if you want to make sure
that all dialogs are destroyed before shutting down completely.
DumThread::shutdown() only stops the process loop thread - there are no
plans to change this that I'm aware of. After you call
DialogUsageManager::shutdown and wait for the callback - you can
shutdown the dum thread anytime, since the tu will have been
unregistered with the stack.
Note: Currently repro implements a "hard" shutdown. The processing
threads are just stopped and the objects destroyed.
> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> Daniel Pocock
> Sent: Saturday, June 24, 2006 9:10 AM
> To: resiprocate-devel
> Subject: [reSIProcate] clean shutdown
>
>
> I'm just wondering if anyone can clarify the following issues, and
> maybe elaborate on them in the Wiki:
>
> a) In a multi-threaded app, does the app have to call both
> DialogUsageManager::shutdown() and DumThread::shutdown()? Should
> DialogUsageManager::shutdown() be called from within the DumThread
> thread of execution? Will DumThread eventually manage all shutdown
> calls?
>
> b) In the repro.cxx code, I notice that DumThread is shutdown after
the
> StackThread. Is there a recommended order for stopping the threads?
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel