[icecast-dev] Server-side streaming roundup

[Vincent-Olivier Arsenault]

  >>Transparent content negotiation
> 
> 
> Meaning?

Well I'm speculating here but, the icecast protocol extends HTTP and 
HTTP provides Accept* headers (locale, content type, encoding, etc).

So for a "/resource" request, any of the following files could be served 
back depending on the client's request, and server's default settings :

"/resource.en.medium.ogg"
"/resource.fr.medium.ogg"
"/resource.en.medium.mp3"
"/resource.fr.medium.mp3"
"/resource.en.low.ogg"
"/resource.fr.low.ogg"
"/resource.en.low.mp3"
"/resource.fr.low.mp3"
"/resource.high.ogg"
"/resource.ogg"
...

Wher the (full) naming scheme is :

"resource name"."locale iso code"."bandwith"."encoding"

That would also affect the metadata.

<p>>>Structured metadata (An XML app would be great)
> 
> 
> icecast2 does this, though it's currently fairly limited. Extending this
> is planned.

Ok, so were should I look, in the code to overview the metadata 
funcionality?

Also, were is the best knowledge base on the icecast/shoutcast protocol?

<p>thanks a million,

<p>vincent

--- >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-dev-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.