We are currently building a system with liquidsoap that we hope to scale to
support hundreds of concurrent streams. We will need to have a large number
of liquidsoap instances to cope with the CPU requirements of all these
streams.
The system is entirely dynamic, so the stations are built dynamically and
tracks pushed to these stations as requests. This does mean that we are
going to have to do some work to manage all the instances of liquidsoap.
One thing I am concerned about is what to do when one of these instances
dies for some reason. As far as I know there is no way to get liquidsoap to
persist its state to allow it to restart (roughly) where it was. So I guess
I'm going to have to store the expected state in the controlling
application and then recreate all the state when an instance needs
restarting. (When I say state, I mean the list of active queues, requests
and icecast outputs)
Does this sound like the best way to approach this, or does anyone have any
better suggestions?
Thanks
Chris
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users
