[icecast] Fallback behaviour
gshang at pacific.net.au
Fri May 21 17:43:04 PDT 2004
I'm looking at Icecast's fallback behaviour, particularly with the fallback
override fuctionality that's in SVN Icecast. Everything works well *if*
connect the client whilst the primary stream is connected. When that
source drops out, you fall through to the backup, and you get pulled
forward when it reconnects. All well and good. But if you try to connect
when the primary stream is not connected, Icecast returns a source not
found and leaves it at that.
Is this the intended behaviour? There may be some good reason for this
behaviour, but I personally can't think of one. Surely part of the point of
this functionality is to have a single mount that listeners can connect to.
Now I know I could set up a relay from one mount to another and put my
primary source on at the time the relay is set up, but this would seem like
a bit of overkill and also a bit of a cludge. And daisy-chaining fallbacks
would be made infinitely more difficult to set up.
--- >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.
More information about the Icecast