DBusGProxy issues

Colin Walters walters at verbum.org
Thu May 13 13:48:51 PDT 2010

On Wed, May 12, 2010 at 12:40 AM,  <raveendranath.kondrakunta at wipro.com> wrote:
> So, what happens is that Process A waits for the timeout of 45 secs and then
> returns a error message. But, the expectation is that Process A should come
> out the call immediately, as Process B died.

Are you using dbus_g_proxy_call?  In that case it's hard; we'd need to
have libdbus itself monitor NameOwnerChanged in a rather hacky way,
and it wouldn't be reliable.

I'd recommend using async cals (_call_async) so that your server
process doesn't block if one of the clients dies.

More information about the dbus mailing list