Hi David,
Regarding the icecast callback on failed connects.
Ill give you the scenario: We have started dynamically generating our
liquidsoap script files. What happens is that the Airtime interface lets you
choose how many streams you want and all the extra details (mountpoint,
icecast host/port, icecast password etc.), And everytime the user saves his
settings the liquidsoap script is regenerated and liquidsoap restarted.
Now the problem is we don't know how to tell the user if his settings are
incorrect. For example did he enter his password correctly? If we knew this
information we could have liquidsoap pass it back by calling an external
system script (its getting complicated I know :/)
Anyway, in the case of an incorrect password, I don't see the need for
liquidsoap to keep polling and attempting the connection to icecast over and
over again. I think the best way would be to create a
autoreconnect=true|false parameter so the user can choose this behaviour.
Otherwise if autoreconnect=false, then allow us to specify a function
callback which is provided information about the failure (icecast connection
error codes?) or server not found?
Martin
2011/9/21 David Baelde <david.bae...@gmail.com>
> 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
>
--
Martin Konecny
Software Developer, Sourcefabric
martin.kone...@sourcefabric.org
720 Bathurst St. Suite 203
M5S 2R4, Toronto, ON, Canada
+1 (416) 892-8420 (Cell)
Skype: martin.konecny15
http://www.sourcefabric.org
http://www.twitter.com/Sourcefabric
------------------------------------------------------------------------------
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
