C-API
Thiago Macieira
thiago at kde.org
Thu Oct 12 11:03:41 PDT 2006
Havoc Pennington wrote:
>Thiago Macieira wrote:
>> The thread solution doesn't really work. We've talking about that on
>> IRC and code inspection revealed that any blocking sends performed in
>> other threads will not work -- the transport is locked.
>
>To be clear, this is a bug, not by design...
I wouldn't classify it as a bug. dbus_connection_read_write_dispatch can
block.
When it blocks, it blocks. It can't be woken up by other threads. If it
could, then libdbus-1 would have to work out which thread would get
access to messages first. What would happen if the wrong thread popped
and processed the reply that another thread was waiting for?
No, it's too complex a solution for libdbus-1 when a simple mainloop
implementation (even in a thread) is enough to solve the problem.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/dbus/attachments/20061012/581bfc57/attachment.pgp
More information about the dbus
mailing list