Icecast - Aug 2004 - strange way of forwarding to another stream.

-----Original Message-----
From: owner-icecast@xiph.org [mailto:owner-icecast@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@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.

> 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?
<p>Yes, that's what I meant (on a second reading, it wasn't very
clear. Sorry).

For the case of moving a client _after_ initial connection, you can't use
HTTP
redirects even for those clients that do support them correctly, so this sort
of mechanism (internally moving them from one source to another) is neccesary
either way.

Mike

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

Hi:

If you want to play 1 stream then play another, surely it's enough to
simply place 2 items in the playlist file that you send to the client.  It
works and it's supported.

Geoff.

<p>
-- 
Geoff Shang <gshang@uq.net.au>
ICQ number 43634701

Make sure your E-mail can be read by everyone!
http://www.betips.net/etc/evilmail.html

Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html

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

Just a follow up to this, Geoff...
True, that is how you'd do it when you know what *n* number of
streams/files you wished to serve at the time the client d/l's the
playlist.  There are cases when you may wish to dynamically change what
the client hears (live radio for instance, or maintenance, etc.) without
requiring the client to manually reconnect.  Redirects would/could be
handy _IF_ clients supported them universally. Alas.

Icecast supports moving clients to new streams (very cool BTW), and that
serves the same purpose - although not as flexible as redirects could be
(if the "new stream" was on a different Icecast instance (or computer)
for example).

Cheers and keep up the great work.

Todd

PS - Michael, you send a lot of early morning emails so watch you don't
burn yourself out!!! ;)

Oh and FWIW, I offer up my C# knowledge/coding/time if it could be of
use in some aspect to you all.  Although I doubt it would be, I wanted
to throw it out there anyway.
> If you want to play 1 stream then play another, surely it's 
> enough to simply place 2 items in the playlist file that you 
> send to the client.  It works and it's supported.
> 
> Geoff.
--- >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.