D-Bus best practices

[Colin Walters]

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?