[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freedesktop-dbus
Subject:    Re: dbus_connection_send_with_reply_and_block and unrelated messages
From:       Thiago Macieira <thiago.macieira () trolltech ! com>
Date:       2006-05-28 20:51:41
Message-ID: 200605282251.49371.thiago.macieira () trolltech ! com
[Download RAW message or body]


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

[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]