Object paths naming conventions?
dbus at matthew.ath.cx
Fri Jul 18 08:43:08 PDT 2008
On Fri Jul 18 17:40, Marcel Holtmann wrote:
> and I think that is a bug within the bindings. The bindings job should
> be actually abstract from this usage and make it possible for two
> unrelated codepaths to register interfaces on the same object path.
I disagree strongly, I think the object model that DBus presents is that
of registering _objects_, not interfaces. I think we have had
discussions before that you should not expect the introspection data on
an object to change without warning, to allow caching.
> In BlueZ we actually allow plugins to register additional interface on
> top of an already established object path. This makes it easy to extend
> everything with lets say a debug interface. The codepaths are unrelated
> and we can have a nice separation inside the core and not bloat it if
> this extra functionality is not desired.
Extend dynamically at runtime?
Implementation details aside, I don't think you should expect this to
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
Url : http://lists.freedesktop.org/archives/dbus/attachments/20080718/21011850/attachment.pgp
More information about the dbus