I haven't looked at the code so forgive me if this is already what it's
doing..
Considering the problems with the current metadata implementation..
couldn't it be changed to just cache the data that comes from the source in
order to update it if it changes, and then just send it down to the
listening clients then in the form of an ID3V2 tag when they first connect,
and then only when it changes?
I'm not entirely sure if they would show the data, but I think they would..
and if they don't, it won't hurt anything, since they don't contain
a valid
sync sequence.
I don't use X on any of my freebsd boxes and thus don't have a
half-decent
gui to try this on myself.. but I may try and compile it under windows with
BC5 which I do have on my windows box. If it works without too much
hassle, I'll try and come up with a patch if none of the project coders are
willing to do it.
-------signature file-------
PGP Key Fingerprint:
446B 7718 B219 9F1E 43DD 8E4A 6BE9 D739 CCC5 7FD7
"I don't think [Linux] will be very successful in the long run."
"My experience and some of my friends' experience is that Linux is
quite
unreliable. Microsoft is really unreliable but Linux is worse."
-Ken Thompson, Interview May 1999.
http://www.freebsd.org
FreeBSD - The Power to Serve
http://www.rfnj.org
Radio Free New Jersey - 445 streams - 40kbps @ 22khz Stereo
http://namespace.org -- http://name.space
Resist the ICANN! Support name.space!
--- >8 ----
List archives: http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to
'icecast-request@xiph.org'
containing only the word 'unsubscribe' in the body. No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.
