Hi, some thoughts from my side when reading through this thread
1) Changing the protocol and cleaning up the API at the same time seems complex to me. What about separating this steps? 2) protocol: What about keep it simple using HTTP/GET requests with JSON responses using the current server commands like http://localhost:8001/station1.start http://localhost:8001/substract(23,42) where 'station1.start' and 'substract(23,42)' are server requests using the current API syntax, hostname and 8001 the hostname and 8001 the server port? JSON-RPC looks not that readable to me --> {"jsonrpc": "2.0", "method": "subtract", "params": {"subtrahend": 23, "minuend": 42}, "id": 3} (see Examples at http://groups.google.com/group/json-rpc/web/json-rpc-2-0 ) With JSON-RPC playing around with the server API would not be as easy as today: I would use a JSON-RPC lib for testing simple RPCs to avoid API syntax errors. Using HTTP/GET would allow to interact with liquidsoap at your browsers URL field as you can do with telnet today. HTTP/GET requires URL escaping for inter-process communication, browser escape themself when typing commands at the URL field. 3) interface stability: I am very happy of using a stable interface for a long time now. (Migration to 9.3 took me some time). I frequently update from HG without bother about possible interface changes. I am not a liquidsoap guru, but I after working with liquidsoap for more than 1 year I learned how to use it. If you feel a strong need of changing the API, just do it, but please consider the migration efforts at user side: e.g. we use different liquidsoap scripts for different purposes on several systems and stations. BR, Peter ------------------------------------------------------------------------------ Storage Efficiency Calculator This modeling tool is based on patent-pending intellectual property that has been used successfully in hundreds of IBM storage optimization engage- ments, worldwide. Store less, Store more with what you own, Move data to the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/ _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
