Object paths naming conventions?
marcel at holtmann.org
Thu Jul 17 15:29:32 PDT 2008
> Thank you, I appreciate the clarification. In a similar way, the
> objects can be reached by the well-known name, the unique connection
> name (e.g., :1.15); plus any additional well-known names the process may
> However, what I thought I was trying to convey is NOT that "/" (or any
> other path) is now owned globally by org.bluez, but that it must be
> unique within org.bluez Is that correct?
yes, that is correct. Object paths are unique to the process.
> Incidentally, it does appear (my experimentation) that DBus allows for
> some polymorphism in method calls (e.g., optional parameters). Is this
> intentional? It also appears that the some/most of bindings do not
> support this...
The reason for this is that most bindings can not deal with dynamic or
shadowing parameter lists.
More information about the dbus