Hi! 2012/5/21 Chris Rimmer <[email protected]>: > Thanks for that! I checked out the latest source from Hg and it seems to > work.
Cool! > Now I have another question! The dynamic queue I am building contains files > served up over http and the queue can get a "skip" message at any time. If I > start streaming one file and do a skip, liquidsoap gets very unhappy because > it hasn't yet pulled the file down from the network. In fact, I've had my > stream broken and messages like "Error while sending data: could not write > data to host: Broken pipe in write()!" appearing in the logs. > > I would like to ensure that the next request in the queue is always > available, but calling request.queue or request.equeue only allows a time to > be specified, not a number of requests. > > Any ideas what I should try next? Try passing conservative=true to your queued sources. This should tell the source to always have one or more request in the queue at any time. Romain ------------------------------------------------------------------------------ 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
