[reSIProcate] question and a request
Leon Thrane
sipfoundry-1 at thrane.net
Wed Aug 24 05:34:27 CDT 2005
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20050824/0010b306/attachment.htm>
More information about the resiprocate-devel
mailing list