if i remember we had discussed the fact that when all your interaction with a file is
local it makes sense to just store info on the end. a streaming server should be able
to rearrange the data prior to sending it to optimize streaming.
elrod
Scott Thomas Haug wrote:
> On Sat, 23 Oct 1999, Brett Thomas wrote:
> > On Sat, Oct 23, 1999 at 09:55:36PM -0500, Scott Thomas Haug wrote:
> > > up with a library for easily parsing that info as well. The format is no
> > > work of art, but it does have some benefits over id3v2: the tag as a whole can
> > > vary in size, it comes at the end of the file, and is reasonably easy to parse.
> >
> > Everything there sounds cool except "at the end of the file." The
> > metadata should go at the beginning, so that you know what the song is
> > BEFORE you just spent twenty minutes downloading the whole thing. :)
> >
> > Brett
>
> Actually, if it were up to me, I would have include tag information at the
> beginning and the end. Information that isn't likely to change or isn't too
> big (artist, song title, source, etc.) would go at the beginning (along with
> some padding to allow for some change w/o having to rewrite entire file)
> basically for the reason you give, and everything else (images, information
> that might change frequently) would go at the end of the file. Best of both
> worlds kinda thing. Downside is implementation would be trickier.
>
> -Scott
