dbus_connection_send_with_reply_and_block and unrelated messages

[Thiago Macieira]

Havoc Pennington wrote:
>The basic intent is that anytime you have dbus read from the socket
>(which would include all blocking functions, and an explicit
>dbus_connection_read_write), you need to check the dispatch status prior
>to returning to poll/select.
>
>So the above is one approach, you can also use get_dispatch_status() or
>the set_dispatch_status_func() as two ways to get the dispatch status
>without having to actually dispatch. The dispatch_status_func is called
>in all kinds of crazy contexts so I would be sure to only _queue_
>dispatch in there, don't try to actually dispatch or the reentrancy will
>get dangerous.

Thanks, that clarifies things. I see only one other place that will 
require me to queue a dispatch.

-- 
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
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/dbus/attachments/20060528/192f1e70/attachment.pgp