Hi Martin, 2011/9/21 Martin Konečný <martin.kone...@sourcefabric.org>: > As for the feature request, one of our new developers has been working > extensively with Liquidsoap and has asked if an error callback for attempted > connections is available for output.icecast. I see that there is on_connect > and on_disconnect, but I don't see anything related to callback on > connection errors. Perhaps there is a different way to find out that there > was an error and why it happened?
If you want to trigger an action for every failed connection, without stopping the polling process which tries to reconnect, then it does look like we need a new hook. Is it what you need? If so it should be an easy patch (please consider proposing a first version, it would save us some time). If you're in a different context (no polling, dynamic output creation/deletion) then we may need something fancier. By the way, we are currently exploring a related issue with Martin Hamant. It has to do with handling the failed initialization of an icecast output (in the context of dynamic output creation); currently, an icecast output does not initialize if it can't connect (this is somehow inherited from the simple time where output initialization was done on liquidsoap startup, and failing was good for informing the user that there might be a problem with his script or system). Cheers, -- David ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Savonet-users mailing list Savonet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/savonet-users
