Icecast - Apr 2005 - Adding authenticated mountpoints

Karl Heyes wrote:
> A container from nullsoft
hm, I learn something new every day :)
>>so when the source client logs in, it lies to icecast, saying it's
an
>>mp3 stream? (as icecast won't accept anything else, but mp3 or ogg
>>vorbis...)
> 
> no, a source client identifies itself with a mime-type. MP3 being the
> default handler. Being the default handler means that pass through
> occurs
well, it says: mp3, when it isn't.

but then again, I'm not a crusader, what do I care :)
(and all those poor icecast servers, believing they stream mp3, oh my.. :)

On Mon, 2005-04-11 at 21:35, Akos Maroy wrote:
> Karl Heyes wrote:
> >>so when the source client logs in, it lies to icecast, saying
it's an
> >>mp3 stream? (as icecast won't accept anything else, but mp3 or
ogg
> >>vorbis...)
> > 
> > no, a source client identifies itself with a mime-type. MP3 being the
> > default handler. Being the default handler means that pass through
> > occurs
> 
> well, it says: mp3, when it isn't.
> 
> but then again, I'm not a crusader, what do I care :)
> (and all those poor icecast servers, believing they stream mp3, oh my.. :)
originally it was mp3 only, but we found that if we passed the
mime-types through then AAC and NSV worked :)

yes it could do with being renamed to be say format_generic or some
such, but it didn't seem important at the time.

karl

On Mon, 12 Apr 2005, Karl Heyes wrote:
> My current work is on 
> http://mediacast1.com/~karl/testing/icecast-2.2-kh3pre.tar.gz
Bugs:

	Relays ignore the hidden flag

	HUPing icecast puts icecast in a strange state where it doesn't 
actually take account of the conf changes, and also won't terminate on a 
TERM and needs a KILL - but it does still "work" otherwise.

How is fallback to file actually meant to work ?

I notice you've got fallback-when-full, I would like to fallback (on full) 
to a URL - 302 style - but on a per mount basis rather than setting up a 
whole master/slave relationship.