[icecast] strange way of forwarding to another stream.

[Todd Poston]

-----Original Message-----
From: owner-icecast at xiph.org [mailto:owner-icecast at xiph.org] On Behalf
Of Michael Smith

>>
>> This seems like a very useful thing to be included in a spec.  And it

>> doesn't seem unreasonable to include it in a client, except that
there 
>> is no official spec that stream client developers use to develop 
>> against (or is there??).  Afterall, Things like HTML Redirect's are 
>> handled by the client.
>
>Clients are meant to respond to HTTP (certainly NOT HTML) redirects,
since
>icecast uses HTTP, but most media players don't, so icecast doesn't use
this.
>
>Mike

<homer>D'oh!</homer>.. Can't believe I made such a (now-glaring)
mis-type.. Yes indeed I did mean HTTP redirects and NOT HTML (silly
me!).  I haven't done a lot of testing to see what is and isn't
supported along these lines with the different clients out there, but
FWIW I thought that Winamp (2.x) did support it (but this is going far
back in my memory cells now clouded with too much beer).

When you say that "most media players don't [use this]" I assume you are
refering to the support of HTTP redirects?  And so when you "move"
another client to a new stream, you just grab the bytes from a different
source-stream in icecast and send them down the existing pipe to the
client - rather then sending a redirect causing the client to negotiate
a new request?

Just wanted to be specific for clarification purposes :)
Thanks.

Todd

--- >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 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.