Yes, David's response is 100% right.. I wondered for a while about what to do with this and decided.. to not do anything :-) Here's the reasoning: * Shoutcast protocol is not documented and, apparently, has just changed * I'd rather keep trying to parse a response and keep an eye on shoutcast' response in the future * Metadata updates are "fire and forget" anyway so the error is only informative and cannot be used to fix anything
Thus, I just changed the log message from "this is an error" to "an error may have happened"... I think that's the best for now and the future.. Romain 2011/9/27 David Baelde <[email protected]>: > Romain might have said more about that already in other threads. The > short answer is that the update didn't really fail: the metadata > should be updated, it's just that shoutcast didn't acknowledge it (it > changed behaviour recently) so liquidsoap finds it funny... > > ------------------------------------------------------------------------------ > 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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/savonet-users > ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
