D-Bus best practices

Scott James Remnant scott at canonical.com
Tue Apr 21 11:37:04 PDT 2009

On Tue, 2009-04-21 at 14:28 -0400, Colin Walters wrote:

> On Tue, Apr 21, 2009 at 4:06 AM, Scott James Remnant
> <scott at canonical.com> wrote:
> > On Mon, 2009-04-20 at 21:32 +0200, Thiago Macieira wrote:
> >
> >> b) timeouts: D-Bus method calls *do* timeout. There's no way around this, so
> >> any call that can potentially take some time to execute should be designed in
> >> a call/callback pattern: the call replies whether the action was initiated
> >> and a signal reports the end result.
> >> [This is an area where the protocol itself could use future improvement]
> >>
> > There are patches that have been sitting in Bugzilla for some time now
> > that correct this problem, and allow you to have no timeout on message
> > calls.
> One thing I wanted to know (and feel free to followup on the bug), is
> what are some use cases with those?
You make a call to upstart to start a service that takes a time to start
longer than the current very-short D-Bus timeout.

Scott James Remnant
scott at canonical.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.freedesktop.org/archives/dbus/attachments/20090421/cd981213/attachment.pgp 

More information about the dbus mailing list