[Telepathy-commits] [telepathy-spec/master] Handler: explain what we mean by "incoming" and "outgoing"
Simon McVittie
simon.mcvittie at collabora.co.uk
Fri Sep 26 08:21:43 PDT 2008
---
spec/Client_Handler.xml | 11 ++++++++---
1 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/spec/Client_Handler.xml b/spec/Client_Handler.xml
index ce09570..e89280e 100644
--- a/spec/Client_Handler.xml
+++ b/spec/Client_Handler.xml
@@ -31,7 +31,9 @@
channel bundle; a typical channel handler is a user interface
process handling channels of a particular type.</p>
- <p>When a new incoming channel is offered to
+ <p>When a new incoming channel (one with
+ <tp:dbus-ref namespace="org.freedesktop.Telepathy.Channel.FUTURE">Requested</tp:dbus-ref>
+ = TRUE) is offered to
<tp:dbus-ref namespace="org.freedesktop.Telepathy.Client">Approver</tp:dbus-ref>s
by the channel dispatcher, it also offers the Approvers a list of all
the running or activatable ChannelHandlers whose
@@ -40,9 +42,12 @@
are able to handle the channel. The Approvers can choose one of
those channel handlers to handle the channel.</p>
- <p>FIXME: interaction with outgoing channels?</p>
+ <p>When a new outgoing channel (one with
+ <tp:dbus-ref namespace="org.freedesktop.Telepathy.Channel.FUTURE">Requested</tp:dbus-ref>
+ = FALSE) appears, the channel dispatcher passes it to an appropriate
+ channel handler automatically.
+ </p>
- <p>FIXME: interaction with automatically created channels?</p>
</tp:docstring>
<property name="HandlerChannelFilter" type="v" access="read">
--
1.5.6.5
More information about the Telepathy-commits
mailing list