[xiph-rtp] Difficulties with several RTP streams for a Vorbis stream.

[Aaron Colwell]

True, but just because the client makes a request, it doesn't mean that the
server will get that request. Say the server does get the request and sends
the codebook. It has no way to know whether the client that made the request
got it. What is supposed to happen next? Is the client supposed to make 
another request? Periodic transmisson avoids these problems at the expense of
bandwidth. Periodic transmission of an http URL to the codebook minimizes the
extra bandwidth needed. Current HTTP proxies and caching infastructure can
help with scaling codebook distribution. For one-way distribution like 
satellite, you'll just have to bite the bullet and dedicate a portion of the
total transmission bandwidth to periodic codebook transmission or only use 1
codebook for that broadcast and provide a reliable means for retreiving the
codebook.

Aaron

On Tue, Nov 02, 2004 at 01:13:25AM +0100, Ram?n Garc?a wrote:
> An important difference between between waiting client requests (with
> an enforced interval to limit traffic) and just listenting to RR of
> new clients, is that in the former case codebook transmission is
> avoided if the client does already have it stored.
> 
> Ramon
> _______________________________________________
> xiph-rtp mailing list
> xiph-rtp at xiph.org
> http://lists.xiph.org/mailman/listinfo/xiph-rtp
>