<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
In my case that's not needed, but yes it would be really nice if all
mount options could be retrieved from the database using an
Stefan de Konink wrote:
<pre wrap="">On Fri, 8 Sep 2006, Klaas Jan Wierenga wrote:
<pre wrap="">I guess if the <authentication type="url> section could be used as a
top-level tag (instead of as a sub-tag of <mount>), then that could do
the trick. The mount_add URL would be used to check the validity of
the/any mountpoint. The listener_add authenticates the users.
Would this be hard to implement? It would certainly make administration
a lot easier for icecast users that keep mountpoint names, username and
passwords in a database.
Any help would be appreciated.
I think the implementation is not that hard, but is this the only thing
you want to store for your customer, not things like: bandwidth, max
Probably it could be more easy to store all mounts in SQL, and fetch
info on aauthentication.