[NUT-devel] Broadcast sufficiency - my assumptions/reasoning/design for it
Michael Niedermayer
michaelni at gmx.at
Wed Feb 6 19:22:14 CET 2008
On Wed, Feb 06, 2008 at 12:43:21PM -0500, Rich Felker wrote:
> On Wed, Feb 06, 2008 at 12:40:53PM -0500, Rich Felker wrote:
> > > Also this would only solve ONE single problem brought up. Your design
> > > still leaves the preload time up to pure luck.
> >
> > If you really need to know a minimum preload time, put it in a
> > protocol header or in the spec for the broadcast constraints.
>
> An info packet field for bitrate information, including minimum
> preload, would be totally acceptable too if you like.
The preload changes depending on buffer fullness thus is not constant
over a stream.
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Dictatorship naturally arises out of democracy, and the most aggravated
form of tyranny and slavery out of the most extreme liberty. -- Plato
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.mplayerhq.hu/pipermail/nut-devel/attachments/20080206/fe6c43c8/attachment.pgp>
More information about the NUT-devel
mailing list