[vorbis-dev] RFC draft for Vorbis over RTP

[Maik Merten]

Gregory Maxwell wrote:
> Thus my statement that you could use existing scalability mechnisms... If
> you don't have access to something like that and there will be thousands
> of clients you're free not to provide http access to the headers. The
> disadvantage is that clients will get no audio unless they have the
> headers cached until you retransmit them.
> 

So the proposed system would be something like this?

* The Client connects to the streaming server (e.g. using TCP)
* The server sends header-information
(* TCP-connection gets closed? Perhaps not a good idea - the connection 
can be used for fallback-header-transport avoiding additional handshaking)
* Client receives audio-data over an unreliable transport mechanism

If a new header is necessary:

* Server transmits the header using the unreliable transport mechanism
* Client buffers header-data
* If the header is not transmitted (properly) the client can detect this 
and request them using a reliable transport mechanism (fallback)

<p>Maik


-- 
EN: Every mail bigger than 35 KByte will be deleted automatically from 
my mailbox. Please contact me before sending any attachments.
DE: Jede Mail größer als 35 KByte wird automatisch aus meinem Postfach 
gelöscht. Bitte kontaktieren Sie mich, wenn Sie Anhänge schicken wollen.
--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'vorbis-dev-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.