Wierd interaction between calls to the bus and subsiqent Pending Calls

Havoc Pennington hp at redhat.com
Sat Dec 17 09:09:57 PST 2005


On Sat, 2005-12-17 at 16:03 +0100, Kevin Krammer wrote:
> > However, it's also a bug if the pending call isn't immediately notified
> > after the blocking completes.
> 
> I was talking about the second case.
> However I do not think it's a bug:
> 
> the pending result is received but not dispatched due to the blocking call. 
> After processing the blocking result the application returns to the event 
> loop.
> 
> How would the dbus library dispatch the stored pending result if it is not 
> called?
> IMHO it is the responsibility of the application to check for stored pending 
> results after doing a blocking call if it hasn't received all expected ones 
> yet.

When I said "immediately notified" I meant "the next time you dispatch
or ask for the result," sorry for being confusing :-P

Havoc




More information about the dbus mailing list