Object paths naming conventions?
marcel at holtmann.org
Sat Jul 19 04:52:03 PDT 2008
> > So the object path + interface name represents to me an unique instance
> > where I can have method calls on. With a different interface name, but
> > the same object path is becomes a total different instance.
> Let's take a scenario to clarify this:
> I have a daemon, which implements both bluez and mpris spec (two specs
> with "/" as the object path).
> What do I get if I use the org.freedesktop.Introspectable.Introspect()
> method to query introspection data?
> Do I get a merge of the two implemented interfaces, as expected with
> the D-Bus way?
you get the introspection data for both interfaces.
> Or do I get just the introspection data for the Introspectable
> interface, as you suggest with defining same object path with
> different interfaces as separate instances?
Instances are not D-Bus object paths. What the client sees as instance
is different. For a client the unique instance is the object path plus
the interface name.
More information about the dbus