[reSIProcate] Eventdriven TransactionUser

[Scott Godin]

Although not event driven...   You can use fifo::getNext(timeoutMs) to block on the TU fifo so that you don't need to poll - see DialogUsageManager::process(int timeoutMs).

________________________________

From: resiprocate-devel-bounces at list.resiprocate.org on behalf of Brekke, Tor
Sent: Wed 1/31/2007 7:00 AM
To: resiprocate-devel at list.resiprocate.org
Subject: [reSIProcate] Eventdriven TransactionUser



The resiprocate interface supports event driven communication from the
transaction user to resiprocate through the Interruptable Stack thread.
In the other direction I have not been able to find a similar function,
meaning that the Transaction User will have to poll the message queue to
receive messages. In our current implementation we needed to get rid of
the polling. We therefore added a virtual message notification function
to the transaction user. I have two questions:

1) I feel that there should have been an interruptable call-back
mechanism also to the transaction user. Have i missed anything?

2) If there is no call back mechanism, we have a two-line (obvious)
patch for TransactionUser, which allows the actual transaction user to
implement its own message notification handling. This generates little
overhead when not used. Is there any interest in such a mechanism? If so
I would be happy to provide the patch.


Best Regards
Tor Brekke
Paradial AS

_______________________________________________
resiprocate-devel mailing list
resiprocate-devel at list.resiprocate.org
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20070131/00ffffa9/attachment.htm>