Object paths naming conventions?

David Stockwell dstockwell at frequency-one.com
Thu Jul 17 17:28:16 PDT 2008

Hello again, Marcel,

> Hi David,
>> 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
>> own.
>> 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.

Understood...(we did address this before).
> Regards
> Marcel

I must confess that to some extent, I enjoy stirring the pot a bit to 
see what comes "bubbling up out of the stew".  At the same time, I 
always learn something new from them.

All the best,

More information about the dbus mailing list