[NUT-devel] Re: FINALIZE NUT SPEC!!

Michael Niedermayer michaelni at gmx.at
Tue Feb 28 02:10:11 CET 2006


Hi

On Mon, Feb 27, 2006 at 02:30:23PM -0500, Rich Felker wrote:
> Moving to nut-devel list...
> 
> On Mon, Feb 27, 2006 at 08:08:55PM +0100, Michael Niedermayer wrote:
> > yes, but that realtime data could very well become available afterwards
> > lets say some realtime news of a earthquake, its magnitude, number of
> > casualties and so on wont be known immedeatly
> > furthermore estimates will change, and if you dont like that example, take
> > any other realtime stream (some DJ with music videos whatever) where info
> > is added in realtime some mistakes will creep in and it should be possible
> > to correct them, in such a way that automatic remuxing updates all info
> > thats not hard but with our strict rules its impossible. so with these
> > restrictions i see no sense in info streams
> 
> OK, how about this: drop the requirement that they be
> binary-identical, and instead the last packet with the given
> chapter_id is the one that's valid. Keep the rest of the semantics for
> what range it applies to. This allows updating/correcting info in a
> live stream and will give the correct results if you convert it to an
> info packet for permenant storage (using the latest/most correct
> data). Also this allows you to specify length if it becomes known.

ok

[...]

-- 
Michael




More information about the NUT-devel mailing list