[Telepathy-commits] [telepathy-spec/master] StreamedMedia: remove "lowering barrier to entry" wording
Simon McVittie
simon.mcvittie at collabora.co.uk
Tue Mar 24 09:46:05 PDT 2009
This would allow installation of a client A (that handles audio only) to
break an unrelated client B's video support, if B relied on this. As a
result, nobody can rely on this mechanism, so it's useless.
---
spec/Channel_Type_Streamed_Media_Future.xml | 15 ---------------
1 files changed, 0 insertions(+), 15 deletions(-)
diff --git a/spec/Channel_Type_Streamed_Media_Future.xml b/spec/Channel_Type_Streamed_Media_Future.xml
index 178bdde..5b75c5f 100644
--- a/spec/Channel_Type_Streamed_Media_Future.xml
+++ b/spec/Channel_Type_Streamed_Media_Future.xml
@@ -128,21 +128,6 @@
like XMPP, need this information to advertise the appropriate
capabilities for their protocol.</p>
</tp:rationale>
-
- <p>If { ChannelType = StreamedMedia } is passed to
- SetSelfCapabilities, but no more specific channel class for
- audio or video has been passed to that method (in the presence
- of a ChannelDispatcher, this would mean that there is at least one
- client with that channel class in its HandlerChannelFilter, but
- no installed client has the more specific channel classes in its
- HandlerChannelFilter), then the connection manager SHOULD advertise
- support for every content type (audio or video) that it
- supports.</p>
-
- <tp:rationale>
- <p>This lowers the "barrier to entry" by allowing a simple client
- to say merely that it supports streamed media at all.</p>
- </tp:rationale>
</tp:docstring>
</property>
--
1.5.6.5
More information about the telepathy-commits
mailing list