Hi, I have read alot of the archives, and looked over the development of listener authentication, and wondered if anyone has a working version with MySQL enabled ? as it seems more in 'development' however I would like to give it a try. Any pointers appreciated, or patches I can apply ... to the current 2.2.0 release. Also any thoughts on doing a http style, I have seen one mention of it, but cant find it, ie. making a http request, with say GET /<definable-string-containting-mountpoint> Authorisation: Basic <blah> Agent: Icecast Just curious, as it may allow integration some segments of the market. regards, Andrew.
On Thu, 30 Dec 2004 23:49:43 +0000 (GMT), andrew@tranceairwaves.com <andrew@tranceairwaves.com> wrote:> Hi, > I have read alot of the archives, and looked over the development > of listener authentication, and wondered if anyone has a working version > with MySQL enabled ? as it seems more in 'development' however I would > like to give it a try.I haven't heard of anyone using mysql for anything directly with icecast (people use it for playlist automation systems external to icecast, though).> > Any pointers appreciated, or patches I can apply ... to the > current 2.2.0 release. > > Also any thoughts on doing a http style, I have seen one mention > of it, but cant find it, ie. making a http request, with say > > GET /<definable-string-containting-mountpoint> > Authorisation: Basic <blah> > Agent: Icecast > > Just curious, as it may allow integration some segments of the > market.It isn't clear what you're trying to ask here. All authentication in icecast (except when in backwards-compatibility modes for other protocols) in done using HTTP Basic auth. Mike
> I haven't heard of anyone using mysql for anything directly with > icecast (people use it for playlist automation systems external to > icecast, though).mmm, i thought some of the listener authentication has been looked at with this ? ie. listener wants to connect, provides username,passowrd in URL, icecast goes and looks in a MySQL database. Obviously got the wrong end of the stick here, sorry.>> GET /<definable-string-containting-mountpoint> >> Authorisation: Basic <blah> >> Agent: Icecast >> >> Just curious, as it may allow integration some segments of the >> market. > > It isn't clear what you're trying to ask here. All authentication in > icecast (except when in backwards-compatibility modes for other > protocols) in done using HTTP Basic auth.Okies, very much like my comments above, but instead of Icecast connecting to MySQL it makes a HTTP request, with the credentials provided, and gets back, say 200 (OK) or 401 or 404, from the remote HTTP server, thus letting the user listen or not, or sending back 404 or 401 to the client etc. Hope i am being clear here :) ? regards, Andrew.
On 30 Dec 2004, at 23:58, Michael Smith wrote:> On Thu, 30 Dec 2004 23:49:43 +0000 (GMT), andrew@tranceairwaves.com > <andrew@tranceairwaves.com> wrote: >> Hi, >> I have read alot of the archives, and looked over the >> development >> of listener authentication, and wondered if anyone has a working >> version >> with MySQL enabled ? as it seems more in 'development' however I would >> like to give it a try. > > I haven't heard of anyone using mysql for anything directly with > icecast (people use it for playlist automation systems external to > icecast, though).*holds hand up* We tried out Karl's URL based auth scheme talking to a MySQL DB, to serve premium pay content ('radio'-style sports commentary on that strange English game called cricket). The basic concept rocks utterly, but we did run into some stability problems - this was kh58 - which unfortunately due to pressures of having Real Customers we had to scrap in favour of a cron job that dumped the DB to a flat file and use the basic auth in 2.1. I'll try and thrash the latest kh- branch when I get a chance - it seems that sometimes, a URL-auth request would cause icecast to lock up in a manner that simply stopped it receiving connections, and dumped existing ones.