[PATCH] net-dbus: Raise exception at 'introspector' if network is lost

Pavel Strashkin pavel.strashkin at gmail.com
Mon Nov 28 13:51:27 PST 2011

D-Bus is the protocol with a strict specification. Inside
dbus/dbus-protocol.h i've found the following errors which binding
probably should check for and do nothing:

395 /** Interface you invoked a method on isn't known by the object. */

391 /** Method name you invoked isn't known by the object you invoked it on. */

What do you think?

2011/11/28 Daniel P. Berrange <dan at berrange.com>:
> On Mon, Nov 28, 2011 at 01:38:49PM -0800, Pavel Strashkin wrote:
>> Does it make sense check for another error types which are not related
>> to "introspection is not implemented"? Or NoReply and ServiceUnknown
>> more than enough?
> It is a pretty hard balance to get, because we want to allow use of the
> perl client against apps which do not implement introspection. If we
> treat too many error types as fatal, then we risk making it impossible
> to work against apps which don't support introspection. The two error
> codes we check for so far are targetted enough that they're not a concern,
> but I'm wary of marking more error codes as fatal here.
> Daniel
> --
> |: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
> |: http://libvirt.org              -o-             http://virt-manager.org :|
> |: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
> |: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

More information about the dbus mailing list