diff options
author | Simon McVittie <simon.mcvittie@collabora.co.uk> | 2011-05-17 17:06:46 +0100 |
---|---|---|
committer | Simon McVittie <simon.mcvittie@collabora.co.uk> | 2011-05-17 17:06:46 +0100 |
commit | dd2b63e6e1fa4d773645a94f31709bd0a6eb0152 (patch) | |
tree | 09a703e29b48f72f1439af115ba0299cf3d92787 /doc | |
parent | cd279fd3c57bf60da4436c0fdc15e33735207273 (diff) | |
download | dbus-dd2b63e6e1fa4d773645a94f31709bd0a6eb0152.tar.gz |
Briefly mention why to namespace object-paths
Diffstat (limited to 'doc')
-rw-r--r-- | doc/dbus-specification.xml | 22 |
1 files changed, 21 insertions, 1 deletions
diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml index 20b0d48a..ea72752f 100644 --- a/doc/dbus-specification.xml +++ b/doc/dbus-specification.xml @@ -762,9 +762,29 @@ </itemizedlist> </para> + <para> + Object paths are often namespaced by starting with a reversed + domain name and containing an interface version number, in the + same way as + <link linkend="message-protocol-names-interface">interface + names</link> and + <link linkend="message-protocol-names-bus">well-known + bus names</link>. + This makes it possible to implement more than one service, or + more than one version of a service, in the same process, + even if the services share a connection but cannot otherwise + co-operate (for instance, if they are implemented by different + plugins). + </para> + + <para> + For instance, if the owner of <literal>example.com</literal> is + developing a D-Bus API for a music player, they might use the + hierarchy of object paths that start with + <literal>/com/example/MusicPlayer1</literal> for its objects. + </para> </sect3> - <sect3 id="message-protocol-marshaling-signature"> <title>Valid Signatures</title> <para> |