Re: [reSIProcate] how to queue DumCommands?

["Scott Godin" <slgodin@xxxxxxxxxxxx>]

>From a previous post...
>You can subclass DumCommand and use DialogUsageMaanger::post to queue 
>the message.  The executeCommand method will be called on your object, 
>when dum processes this message.

> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> maodonghu
> Sent: Thursday, August 24, 2006 9:26 PM
> To: resip
> Subject: [reSIProcate] how to queue DumCommands?
> 
> resip
> 
> From the wiki, it said:
> 
> NOTE: There is no threading protection in the DUM methods themseleves.
> If your application itself is multi-threaded you MUST provide your own
> protection (mutexing) if you plan on calling dum->process and/or other
> DUM API's from different threads. This can also be accomplished by
> queueing DumCommands to the dum process loop from your application
> threads.
> 
> Anybody knows how to queueing DumCommands?
> 
> 　　　　　　　　maodonghu
> 　　　　　　　　hhmmdd@xxxxxxx
> 　　　　　　　　　　2006-08-25
> 
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel