here's an idea for icecast.. the ability to create a relay dynamically by passing a url to the admin interface. (instead of having to add to the config file and kill -s HUP) such relays wouldnt be permanently stored in the config file (unless icecast starts writing to its config file) but would function as long as the server stays up, or until stopped thru the admin interface. --mark
On Wed, 2005-05-25 at 22:19, mark burdett wrote:> here's an idea for icecast.. > the ability to create a relay dynamically > by passing a url to the admin interface. > (instead of having to add to the config file and kill -s HUP) > > such relays wouldnt be permanently stored in the config file > (unless icecast starts writing to its config file) > but would function as long as the server stays up, > or until stopped thru the admin interface.not sure this would be worth it, while adding a new relay is possible, you would need to support the setting of the relay options and the mount settings for it. Not impossible but not something that would be implemented quickly. karl.
perhaps "static" relays (those in config file) could also be controlled (turned on/off etc.) thru the admin site. --mark On Wed, 25 May 2005 22:49:53 +0100, Karl Heyes wrote:> On Wed, 2005-05-25 at 22:19, mark burdett wrote: > > here's an idea for icecast.. > > the ability to create a relay dynamically > > by passing a url to the admin interface. > > (instead of having to add to the config file and kill -s HUP) > > > > such relays wouldnt be permanently stored in the config file > > (unless icecast starts writing to its config file) > > but would function as long as the server stays up, > > or until stopped thru the admin interface. > > not sure this would be worth it, while adding a new relay is possible, > you would need to support the setting of the relay options and the mount > settings for it. Not impossible but not something that would be > implemented quickly. > > karl. > >