[Telepathy-commits] [telepathy-spec/master] Client: sketch how we're planning to discover available client processes (prompted by Alban on the mailing list)

[Simon McVittie]

20080610122730-53eee-d5e15a35e24464f3f63bcafcc97e8607464dc54c.gz
---
 spec/Client.xml |   11 +++++++++++
 1 files changed, 11 insertions(+), 0 deletions(-)

diff --git a/spec/Client.xml b/spec/Client.xml
index 7da13c8..72a5df4 100644
--- a/spec/Client.xml
+++ b/spec/Client.xml
@@ -29,6 +29,17 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
       <p>User interface processes are the obvious example of Telepathy
         clients, but they can provide other functionality, such as
         address-book synchronization.</p>
+
+      <p>Every running or activatable process with a well-known
+        name of the form org.freedesktop.Telepathy.Client.something should be
+        probed by the channel dispatcher to discover its capabilities. Each
+        client is either an <em>observer</em>, an <em>approver</em>, a
+        <em>channel handler</em>, or some combination of these.</p>
+
+      <p>As an optimization, we intend to introduce a .client file (similar to
+        .manager files) so that for most clients, the channel dispatcher can
+        just read a file instead of service-activating the client straight
+        away.</p>
     </tp:docstring>
 
     <property name="Interfaces" type="as" access="read"
-- 
1.5.6.5