[Telepathy-commits] [telepathy-spec/master] Client: suggest how non-activatable services can generate unique well-known names if they want instances handled separately

[Simon McVittie]

20080630124449-53eee-b59168cdaed9b89059889f27883ee1150a9346fd.gz
---
 spec/Client.xml |   11 ++++++++++-
 1 files changed, 10 insertions(+), 1 deletions(-)

diff --git a/spec/Client.xml b/spec/Client.xml
index 9f13015..94a959e 100644
--- a/spec/Client.xml
+++ b/spec/Client.xml
@@ -52,7 +52,16 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
       </tp:rationale>
 
       <p>The client name, <em>clientname</em>, MUST be a non-empty string of
-        ASCII digits, letters and/or underscores, starting with a letter.</p>
+        ASCII digits, letters and/or underscores, starting with a letter.
+        For non-activatable services, it MAY contain a part that is generated
+        per instance at runtime.</p>
+
+      <tp:rationale>
+        <p>If each of a client Foo's instances should be able to manipulate
+          channels separately, the instance with unique name
+          <code>:1.25</code> could request a well-known name like
+          <code>org.freedesktop.Telepathy.Client.Foo__1_25</code>.</p>
+      </tp:rationale>
 
       <p>Each Client MUST export an object whose object path may be
         determined by replacing '.' with '/' in the well-known name and
-- 
1.5.6.5