hey there, I, for one, like simple protocols as well. For local network communication I love REST along with JSON. I will surely stand corrected but I couldn't find anything simpler. If I have to go the full RPC way, I personally like Hessian http://en.wikipedia.org/wiki/Hessian_%28web_service_protocol%29 because it's incredibly fast, simple, and libraries have already been implemented in most languages. Not in OCAML last time I checked though. If I may suggest: please no SOAP, Corba, or any other monstrosities of that kind. I hope they will die soon enough.
I've got a tiny Perl adapter running right now on a test machine for evaluation. The purpose of such an extension, on my end, is to allow controlling Liquidsoap's queue and switching between queue mode and live harbour on demand. Nothing else. An obvious prerequisite is that I cannot assume the application that controls Liquidsoap is located on the same machine. It both acts as a server and a client, and communicates: - with Liquidsoap via pipes and your system() bindings, - and with the outside world through a simple REST/JSON webservice layer. It's not blazingly fast, but it's just a few lines of code if you use the LWP and JSON modules for example. I don't know whether it would be worth your time adding this kind of feature directly within Liquidsoap in the end. Just my very humble opinion. -- best regards, okay_awright <okay_awright AT ddcr DOT biz> [PGP key on request] On 20/07/2011 18:10, Romain Beauxis wrote: > 2011/7/20 David Baelde <[email protected]>: >> No definite plans, but I'd really like to rework and cleanup the >> server interface. > > Yeah, we've been looking at this for a while. However, this may > require some significant change in the code. > > A question relative to this that maybe people here can help us > answering is the following: > What would be a nice protocol/API for machine-oriented > communications between liquidsoap and external applications? > > So far I had been thinking of having a complete JSON API, which would > be a translation of the current telnet API. However, some of you have > also mentioned several other protocols which I have never heard of. > > Thus, dear users, what would you like to use for this purpose and why? :-) > > Romain > > PS: Time is a critical issue for us. Any solution with a nice and > simple way to implement in liq would probably be preferred :-) ------------------------------------------------------------------------------ 10 Tips for Better Web Security Learn 10 ways to better secure your business today. Topics covered include: Web security, SSL, hacker attacks & Denial of Service (DoS), private keys, security Microsoft Exchange, secure Instant Messaging, and much more. http://www.accelacomm.com/jaw/sfnl/114/51426210/ _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
