Re: [reSIProcate] question and a request
I have not find anything wrong with your design.
Another thing may worth more considerations:
If you have a lot of buddies in your buddy list, and
use subscription refresh to keep your subscription
active, there may be a lot of processing in DUM. The
same thing applies to registration refresh. In this
case, you may put DUM into a separated thread, and use
FIFO to communicate between your main Window thread
and DUM thread. This kind of communication only
happens when the user interaction is needed for the
incoming message to DUM, for example, receiving an
incoming call, an imcoming instant message. All other
message which doesnot need user interaction can be
handled in DUM thread, for example, subscription
refresh, and registration refresh.
Regards,
kaiduan
--- Leon Thrane <sipfoundry-1@xxxxxxxxxx> wrote:
> I'm using DUM and reSIProcate on WinCE in the split
> thread model (DUM runs
> in the main Window thread and reSIProcate in a
> separate subsidiary thread).
> To avoid unneeded calls to
> 'DialogUsageManager.process ()' in the main
> Window thread I send messages from the subsidiary
> thread to the main thread
> when DUM processing is needed as indicated by
> 'mFifo.messageAvailable ()' in
> the DialogUsageManager.
>
> So, firstly a sanity check. Have I missed something
> or am I right in my
> determination that 'mFifo.messageAvailable ()' is a
> correct test for when
> 'DialogUsageManager.process()' needs to run?
> Assuming that I am right, I
> think it would be appropriate to have a public
> function that allows for this
> test. I have subclassed DialogUsageManager to
> provide that function but
> anybody running in a split threading model would
> likely need the same
> (assuming they worry about efficiency and battery
> life on handheld devices).
>
> inline
> bool
> DialogUsageManager::processNeeded (void) const
> {
> return mFifo.messageAvailable ();
> }
>
>
> If I'm wrong in my determination, could somebody
> please let me know?
>
> Thanks,
> Léon
>
> > _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
>
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
__________________________________________________________
Find your next car at http://autos.yahoo.ca