[xiph-commits] r10577 - trunk/vorbis/doc

[lu_zero at svn.xiph.org]

Author: lu_zero
Date: 2005-12-10 19:14:02 -0800 (Sat, 10 Dec 2005)
New Revision: 10577

Modified:
   trunk/vorbis/doc/draft-ietf-avt-vorbis-rtp-00.xml
Log:
Minor update

Modified: trunk/vorbis/doc/draft-ietf-avt-vorbis-rtp-00.xml
===================================================================
--- trunk/vorbis/doc/draft-ietf-avt-vorbis-rtp-00.xml	2005-12-10 20:15:24 UTC (rev 10576)
+++ trunk/vorbis/doc/draft-ietf-avt-vorbis-rtp-00.xml	2005-12-11 03:14:02 UTC (rev 10577)
@@ -992,16 +992,16 @@
 
 <section anchor="Stream Radio" title="Stream Radio">
 
-<t>That is one of the most common situation: one single server streaming content in multicast, the clients may start a session at random time. The content itself could be a mix of live stream as the dj's speech and stored streams as the music she plays.</t>
+<t>That is one of the most common situation: one single server streaming content in multicast, the clients may start a session at random time. The content itself could be a mix of live stream, as the dj's voice, and stored streams as the music she plays.</t>
 
 <t>In this situation we don't know in advance how many codebooks we will use. The clients can join anytime and users expect to start listening to the content in a short time</t>
 
-<t>On join the client will receive the current Configuration necessary to decode the current stream inlined in the SDP. And can start decoding the current stream.</t>
+<t>On join the client will receive the current Configuration necessary to decode the current stream inlined in the SDP. And can start decoding the current stream as soon it joins the session.</t>
 
-<t>When the streamed content changes the new Configuration is sent in-band before the actual stream, and the Configuration that has to be sent inline in the SDP updated.</t>
+<t>When the streamed content changes the new Configuration is sent in-band before the actual stream, and the Configuration that has to be sent inline in the SDP updated. Since the inline method is unreliable, an out of band fallback is provided. The client could choose to fetch the Configuration from the alternate source as soon it discovers a Configuration packet got lost inline or use selective retransmission{FIXME}, if the server supports them</t>
 
-<t>A serverside optimization would be keep an hash list of the Configurations per session to avoid packing them and send the same Configuration with different Ident tags</t>
-<t>A clientside optimization would be keep a tag list of the Configurations per session and don't process configuration packets already known.</t>
+<t>A serverside optimization would be to keep an hash list of the Configurations per session to avoid packing all of them and send the same Configuration with different Ident tags</t>
+<t>A clientside optimization would be to keep a tag list of the Configurations per session and don't process configuration packets already known.</t>
 
 <t>Let's assume that the client playout buffer can store at least 7 packets.</t>