Dear all,
Along with the exciting features that were released with the previous
1.0 beta version of liquidsoap were a couple of annoying bugs that,
thanks to very valuable feedback from adventurous users, we have been
able to fix!
Therefore, we will be preparing a new bugfix beta in a little while.
In the mean time, you are more than welcome to submit any bug you
experience with the current beta and/or hg code so that we get a
chance to address each and everyone's problem for the next beta!
The bugs
=======
The bugs that we are aware of and that have been fixed in the default
branch now are:
* A proper timeout mechanism for input.http, input.harbor,
output.icecast, output.harbor, telnet server and harbor server was
missing and has just been commited
* input.harbor had troubles reconnecting after a source client left,
either by disconnecting or using the harbor.{kick,stop} server command
* Some text playlists under windows were not properly parsed.
Harbor timeout
===========
Concerning the timeout mechanism, we are wondering what value for the
input.harbor timeout would be ideal as the default. Currently, it is
set to a very high number -- 30 seconds. Most users concerns with
input.harbor issues are those who have DJs with bad connections, where
in this case, the harbor should detect that the connection is down
quite quickly in order to close it and get ready for a new source
connection.
Therefore, if you have time to experiment with different values of the
timeout parameter in input.harbor and report which value you think is
the most sensible as the default, we would be happy to change it if
needed. This, of course, also goes for input.harbor users whose DJs
have good connections: the default should be what we expect to be the
least annoying case for everyone..!
JSON export/import and RPC
=====================
There has been a discussion recently about the possibility to have a
proper RPC protocol for liquidsoap. Although we are not ready yet to
change the current telnet server code, a function for
importing/parsing json data, of_json, using the json-wheel library has
also just been committed.
This function, along with the export function json_of and the harbor
http server offer now the basic bricks needed to build your own
JSON-based RPC server.
However, these are still in a very early stage: you will have to deal
with HTTP responses on your own (see:
http://savonet.sourceforge.net/doc-svn/harbor_http.html) and also some
functionalities from the telnet server, such as accessing
request.{queue,equeue}'s queues are not yet available within the
scripting language.
Online documentation
================
There has been some work done on the webpages, in particular for the
presentation of the API and settings. Users with a javascript-enabled
browser may want to go have a look there:
http://savonet.sourceforge.net/doc-svn/reference.html
and there:
http://savonet.sourceforge.net/doc-svn/settings.html
These improvements are also available in the other versioned
documentations online.
We need you!
==========
Now, its your time to help! If you can, checkout the latest hg default
branch, have it run for a while, write down what works and what does
not and, if shit happens, shoot us a bug report there:
http://dev.sourcefabric.org/browse/LS
If you submit a bug report, please take some time to attach your
script -- as minimal as possible, your logs and a detailed explanation
of what you expect and what you observe.
Thank you for your help and have a great week!
Romain
------------------------------------------------------------------------------
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
http://www.accelacomm.com/jaw/sfnl/114/51385063/
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users
