Calling back to a calling process after dbus_g_proxy_call_no_reply

[Braden McDaniel]

I have a "host" process that initiates an interaction with a "hosted"
process with a call to a method on an object in the hosted process using
dbus_g_proxy_call_no_reply. In response, the hosted process turns around
and calls a method on an object in the host process, but this time using
dbus_g_proxy_call. This call times out; the corresponding function on
the host process' object is never called.

I'd thought that using dbus_g_proxy_call_no_reply in the host process
would leave it free to service a subsequent call from the hosted
process; is this inaccurate?

-- 
Braden McDaniel                           e-mail: <braden at endoframe.com>
<http://endoframe.com>                    Jabber: <braden at jabber.org>