Is there a way to configure the GLib binding in such a way that an incoming message can be preocessed even if the main loop execution is stopped into a synchronous call (waiting for its answer) ? Would that be safe ? I really think using asynchronous calls only would make a system much more complex than it would be if synchronous calls were allowed. Jacques <div>On 3/22/07, John (J5) Palmieri <<a href="mailto:johnp@redhat.com">johnp@redhat.com</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Thu, 2007-03-22 at 19:48 +0100, Thiago Macieira wrote: > Matthew Johnson wrote: > >For those on the list, this thread is about reentrant calls in D-Bus; > >that is when application A makes a call on application B, and > >application B's handler for that call makes another call back to > >application A. Jacques thought this could be handled more nicely if a > >'call trace' was stored in the header of each message so that the second > >call was associated with the first. > > We agreed last year we don't want that. The applications that try to make > this should deadlock visibly during their development phases, so that > developers take the time to make asynchronous calls. > > We reached that conclusion because the "call stack" or similar mechanisms > (like used to exist in DCOP) solve the problem for the simple deadlocks, > but make it a lot harder to spot the more complex ones. And those end up > creeping into the final releases. Yep. async calls solve this problem and others without further complicating D-Bus.  Always use async calls if possible. -- John (J5) Palmieri <<a href="mailto:johnp@redhat.com">johnp@redhat.com</a>> _______________________________________________ dbus mailing list <a href="mailto:dbus@lists.freedesktop.org">dbus@lists.freedesktop.org </a> <a href="http://lists.freedesktop.org/mailman/listinfo/dbus">http://lists.freedesktop.org/mailman/listinfo/dbus</a> </blockquote></div>