Method calls without timeouts

Thiago Macieira thiago at
Fri Jul 18 09:22:29 PDT 2008

Scott James Remnant wrote:
>As discussed earlier on this list, I hereby attach a set of patches that
>permit an application to wait forever for a method reply, and allow the
>bus to apply no expiry to the replies it's tracking.
>This is done by setting the bus config reply timeout to -1 (the new
>default), and by passing INT_MAX to dbus_connection_send_with_reply.
>Your method call with remain pending until the reply is received, an
>error is received, or you or the remote end disconnects.

First of all, you forgot to attach the patch. (You know that KMail warns 
you about that, right?)

Second, I am not sure this is entirely a good thing. I know the bus daemon 
had a reason to have this upper limit, but I really don't remember now. 
Can someone remind us?

In any case, what happens if applications start using very high timeouts 
and no replies come? Won't that start eating up resources on the bus 

Shouldn't we simply add a marker in the message headers saying that no 
timeout handling by the bus daemon is necessary?

  Thiago Macieira  -  thiago (AT) - thiago (AT)
    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: This is a digitally signed message part.
Url : 

More information about the dbus mailing list