[xiph-commits] r10727 - trunk/theora/doc
lu_zero at svn.xiph.org
lu_zero at svn.xiph.org
Tue Jan 10 03:35:23 PST 2006
Author: lu_zero
Date: 2006-01-10 03:35:20 -0800 (Tue, 10 Jan 2006)
New Revision: 10727
Modified:
trunk/theora/doc/draft-barbato-avt-rtp-theora-00.xml
Log:
Example section wip
Modified: trunk/theora/doc/draft-barbato-avt-rtp-theora-00.xml
===================================================================
--- trunk/theora/doc/draft-barbato-avt-rtp-theora-00.xml 2006-01-10 04:31:33 UTC (rev 10726)
+++ trunk/theora/doc/draft-barbato-avt-rtp-theora-00.xml 2006-01-10 11:35:20 UTC (rev 10727)
@@ -941,8 +941,26 @@
</section>
+</section>
+<!-- WIP
+<section anchor="Examples" title="Examples">
+
+<t>
+The following examples are common usage patterns that MAY be applied in such situations, the main scope of this section is to explain better usage of the transmission vectors.
+</t>
+
+<section anchor="Peer to Peer Internet Messaging" title="Peer to Peer Internet Messaging">
+
+<t>This scenario implies two peers linked by a best effort network, the bandwidth isn't guaranteed, in order to keep the latency low enough is necessary to use dynamic adaptation tecniques.</t>
+
+</t>The agents have to agree over a set of bitrates and during the session they switch from higher to lower bandwidth depending on the rtcp feedback changing the payload number within the same rtp session</t>
+
+<t>Since all the codebooks are all known in advance and the payload changes may happen frequently the in-band vector won't be used at all.</t>
+
</section>
+</section>
+-->
<section anchor="Security Considerations" title="Security Considerations">
<t>
More information about the commits
mailing list