[Telepathy-commits] [telepathy-spec/master] req2: propose implementation as per Friday's spec meeting

Simon McVittie simon.mcvittie at collabora.co.uk
Mon Sep 15 08:08:54 PDT 2008


---
 doc/request.txt |   13 +++++--------
 1 files changed, 5 insertions(+), 8 deletions(-)

diff --git a/doc/request.txt b/doc/request.txt
index ef8da65..d81e620 100644
--- a/doc/request.txt
+++ b/doc/request.txt
@@ -105,13 +105,9 @@ Things smcv considered to be problems:
 
   * Resolution: Rob does not consider this to be a problem, overruled
 
-Proposed implementation: (FIXME: assumes existence of EnsureChannelByAccount,
-EnsureChannel)
-
-::
+Proposed implementation::
 
-    address book calls ChannelDispatcher.StartRequest
-    address book calls ChannelRequest.EnsureChannelByAccount(
+    address book calls ChannelDispatcher.EnsureChannel(
         account,
         {
             '...ChannelType': '...Text',
@@ -119,8 +115,9 @@ EnsureChannel)
             '...TargetHandle': romeo,
         },
         timestamp,
-        my_own_bus_name
+        ''
     )
+    address book connects to signals and calls ChannelRequest.Proceed
 
     ChannelDispatcher calls AddRequest on chat UI, which makes a new tab
     (if it is not already handling such a channel)
@@ -153,7 +150,7 @@ and chooses his entry in her address book again.
 
 Proposed implementation::
 
-    initially the same as for req2
+    initially the same as for req2 (until [+])
 
     ChannelDispatcher tells AccountManager to put account online
     ChannelDispatcher calls EnsureChannel ({...same arguments...})
-- 
1.5.6.5




More information about the Telepathy-commits mailing list