[Telepathy-commits] [telepathy-spec/master] req38: add use case: requesting a channel directly from the connection manager without the CD's involvement, and getting the CD to ignore it

[Simon McVittie]

20080630185127-53eee-9e5a29f23e3930dfd47147d10038ed15c32a8423.gz
---
 doc/request.txt |   29 +++++++++++++++++++++++++++++
 1 files changed, 29 insertions(+), 0 deletions(-)

diff --git a/doc/request.txt b/doc/request.txt
index 5042a93..c18f792 100644
--- a/doc/request.txt
+++ b/doc/request.txt
@@ -1218,6 +1218,35 @@ time out after around 25 seconds unless special action is taken
 Proposed implementation: the ChannelDispatcher creates a request "cursor"
 object for the duration of the request
 
+_`req38`: Going behind the channel dispatcher's back
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+A new channel is needed in one of the following cases:
+
+* _`req38a`: A monolithic Telepathy client on a resource-constrained
+  platform interacts directly with the Requests interface to request a
+  channel. There is no channel dispatcher.
+
+* _`req38b`: telepathy-inspector requests a channel which it will handle
+  internally. The channel dispatcher may or may not be installed; if
+  installed, it should not launch any UI for this channel.
+
+Proposed implementation:
+
+* The client calls RequestChannels on the CM directly, setting the
+  SUPPRESS_HANDLER flag
+
+* In case req38b_ the channel dispatcher (if present) runs observers in
+  response to the NewChannel signal, but does not run approvers or a channel
+  handler because the SUPPRESS_HANDLER flag is set
+
+* In case req38a_ the client ignores the NewChannel signal because
+  SUPPRESS_HANDLER is set (which it would not be on incoming channels);
+  in case req38b_ telepathy-inspector logs the event but does not pop up
+  a window in any case
+
+* RequestChannels returns the channel to the client, and it handles it
+
 General issues
 --------------
 
-- 
1.5.6.5