Icecast - Aug 2004 - alias mount points

Geoff Shang wrote:
>Hi:
>
>Someone sent a patch to the development list that would allow you to set up
>a stack of mountpoints, each with precedence over the one below it.  So if
>mount A is connected, listeners would get that, if not, listeners would get
>mount B if it were connected, else C, etc.  Actually I think this much is
>in standard icecast, but the trick to this patch was that if mount A
>reconnected, listeners would be pulled forward again to that mountpoint.  I
>*think* this was committed to subversion, or CVS as it was then.  This
>would probably help you achieve what you want, with your playlist as the
>lowest priority and your other broadcasters higher up.
>
>Geoff.
>  
>
That sounds very close... I'll have to check it out. The main problem I 
could think of would be, with the way our station operates, we have 
potentially hundreds of different DJs connecting to our stream... and 
there's no way to guarantee that all of them will have all of their 
settings correct. Because of this, we have the intermediary step of 
having an admin connect to verify everything before they actually go 
live to the public. I wonder, would this be possible to implement with 
that patch, or would that be too far outside its realm of working?

Also, unique users/passwords would be nice... a custom auth module of 
some sort, perhaps? A database backend, instead of reading the config?

Thanks for the input, I'll see about investigating that some more. 
Please let me know if you have any more ideas on this!

--Joseph Wilhelm
--- >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:

Someone sent a patch to the development list that would allow you to set up
a stack of mountpoints, each with precedence over the one below it.  So if
mount A is connected, listeners would get that, if not, listeners would get
mount B if it were connected, else C, etc.  Actually I think this much is
in standard icecast, but the trick to this patch was that if mount A
reconnected, listeners would be pulled forward again to that mountpoint.  I
*think* this was committed to subversion, or CVS as it was then.  This
would probably help you achieve what you want, with your playlist as the
lowest priority and your other broadcasters higher up.

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.

On Thursday 06 May 2004 13:23, Joseph Wilhelm wrote:
> Also, unique users/passwords would be nice... a custom auth module of
> some sort, perhaps? A database backend, instead of reading the config?
We already have this for listeners (it uses a flat-file backend, storing 
usernames and md5sums of passwords - but the design is such that a database 
backend could also be done fairly easily).

Extending it to be usable for sources should be reasonably straightforward.

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.