thiago.macieira at trolltech.com
Sat Feb 25 17:56:20 PST 2006
Havoc Pennington wrote:
>In your proposal dbus_connection_dispatch() can fully complete the
>dispatch process (trying all the filters/handlers), finding the handler
>that will be used; then unlock, and call that handler again.
>There are several ways I can think of that a handler would know it's
>being called the first time or the second time; any thoughts on that?
I think the most inobtrusive way to do this is to overload
dbus_connection_add_filter into dbus_connection_add_filter2 that takes
two functions as parameters. The second one would be called when the lock
has been released.
>In DBusObjectPathVTable we could put another function to be used the
>second time, but that won't work for message filters, only for
>registered object path handlers...
Yes. I could implement all my parsing in terms of ObjectPathVTable if
that's what it would take, though.
Thiago José Macieira - thiago.macieira AT trolltech.com
Trolltech AS - Sandakerveien 116, NO-0402 Oslo, Norway
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 191 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/dbus/attachments/20060226/6834ccaf/attachment.pgp
More information about the dbus