diff options
| author | Xavier Claessens <xclaesse@gmail.com> | 2011-11-07 16:07:31 +0100 |
|---|---|---|
| committer | Xavier Claessens <xclaesse@gmail.com> | 2011-11-07 16:37:59 +0100 |
| commit | 3620d2d2bb7100a050b2092e6e520ea9e5d6c372 (patch) | |
| tree | 07c343459b9bb74809e06bee68a2a54ff5ca6c2d | |
| parent | fc1e0e904dec17d47ccf4fbf2d8be4213fe291d3 (diff) | |
Call1: Add rational explaining why Content could have multiple streams
| -rw-r--r-- | spec/Call_Content.xml | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/spec/Call_Content.xml b/spec/Call_Content.xml index 12061a29..ef08acc3 100644 --- a/spec/Call_Content.xml +++ b/spec/Call_Content.xml @@ -31,6 +31,17 @@ and one video content. Each content has one or more <tp:dbus-ref namespace="ofdT.Call1">Stream</tp:dbus-ref> objects which represent the actual transport to one or more remote contacts.</p> + <tp:rationale> + There are two cases where multiple streams may happen: + <ul> + <li>Calls with more than two participants, if the protocol does not + support multicast, and does not have mixer proxy.</li> + <li>With jingle, when calling a contact connected from multiple + resources, a stream is created for each resource. Once the remote + contact answered from one of its resources, all other streams get + removed.</li> + </ul> + </tp:rationale> <p>For protocols that support muting all streams of a given content separately, this object MAY also implement the <tp:dbus-ref namespace="ofdT.Call1.Interface">Mute</tp:dbus-ref> interface</p> |