[Telepathy-commits] [telepathy-spec/master] req1: declare selection of channel handler to be out of scope, for the moment. ChannelDispatcher implementations can do this in an implementation-specific way

[Simon McVittie]

20080610162614-53eee-f89f66082eb8ff1e6ee6ab46e31aa0837575cce9.gz
---
 doc/dispatch.txt |    3 ++-
 doc/request.txt  |    7 +++++++
 2 files changed, 9 insertions(+), 1 deletions(-)

diff --git a/doc/dispatch.txt b/doc/dispatch.txt
index 297c71e..6129338 100644
--- a/doc/dispatch.txt
+++ b/doc/dispatch.txt
@@ -82,7 +82,8 @@ Proposed implementation:
 
 * The tray icon is a Client and a Client.Approver
 
-* The chat UI is a Client and a Client.ChannelHandler
+* The chat UI is a Client and a Client.ChannelHandler (selected in an
+  implementation-specific way)
 
 Problems remaining:
 
diff --git a/doc/request.txt b/doc/request.txt
index 643c41f..1ae8052 100644
--- a/doc/request.txt
+++ b/doc/request.txt
@@ -1180,6 +1180,13 @@ object for the duration of the request
 General issues
 --------------
 
+Selecting a channel handler
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+We can solve this later. For now, it's implementation-dependent which
+handler is used if several are possible - the channel dispatcher can use
+any reasonable algorithm to choose one.
+
 Selecting new or existing channels
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-- 
1.5.6.5