Re: Locking

Ross Burton wrote:
>Hi,
>
>I noticed the discussion on dispatch locking has fizzled out, and was
>wondering if:
>
>1) this would solve the deadlock where client calls server, and before
>server returns it makes a call back to client.  Currently this times
>out.

It would solve half of the problem. Currently, IIRC, the server may 
deadlock internally, which means the client times out.

The solution would allow the server not to deadlock internally. But 
whether the two programs together deadlock or not is a matter of 
implementation detail: whether the binding does a blocking wait with 
dbus_send_message_with_reply_and_block or whether it uses an event loop.

If you've got both sides waiting on 
dbus_send_message_with_reply_and_block, they'll deadlock.

The only solution to this, that I can see, is to add a DCOP-style tag to 
the message, indicating that it is being processed in the context of a 
method call.

>2) can I help test any patches?  If the patches would fix this problem
>I'd really like to see it committed soon, as it means I don't have to
>wrap large amounts of code in g_idle_add().

Our first attempt at patching backfired. There are no new patches to be 
tested yet.

-- 
Thiago José Macieira - thiago.macieira AT trolltech.com
Trolltech AS - Sandakerveien 116, NO-0402 Oslo, Norway

pgpDONBS071wh.pgp
Description: PGP signature

_______________________________________________
dbus mailing list
dbus-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@xxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/dbus