Object paths naming conventions?
simon.mcvittie at collabora.co.uk
Sat Jul 19 05:11:56 PDT 2008
On Sat, 19 Jul 2008 at 13:52:03 +0200, Marcel Holtmann wrote:
> 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.
That's not the D-Bus object model, that's *your* object model.
In dbus-glib you do indeed get a DBusGProxy per (path, interface) pair.
This is widely(?) considered to have been a mistake, and all the Telepathy
libraries have bundled together all the proxies for the same path into
one conceptual object again (which leads to a much more sensible API).
In dbus-python you have a ProxyObject per path (there are also Interface
objects that wrap a ProxyObject, as a convenience for calling many
methods on the same interface, but the ProxyObject is the only one with
any significant code).
If I was to rewrite dbus-glib and dbus-python without caring about
backwards compatibility, they would both behave like dbus-python in this
respect. I suspect that dbus-java and ndesk-dbus follow dbus-python's
model too (Matthew? Alp? Do they?).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 155 bytes
Desc: Digital signature
Url : http://lists.freedesktop.org/archives/dbus/attachments/20080719/7fc9677b/attachment.pgp
More information about the dbus