Re: [Qemu-devel] [PATCH 01/11] QMP: Introduce specification file

[Anthony Liguori <anthony@codemonkey.ws>]

Vincent Hanquez wrote:
> On Tue, Jun 23, 2009 at 05:50:24PM -0500, Anthony Liguori wrote:
>   
>>> this one is mentioned on the website and has been changed recently (may 2009):
>>>
>>> http://fara.cs.uni-potsdam.de/~jsg/json_parser/
>>>   
>>>       
>> That's not a jsonrpc library, that's just a json parser.
>>     
>
> but this is completly trivial at this point. jsonrpc is a json message put in a
> certain way.
>
> now providing there was a maintained library out there, would you use it ?
> or do you have more concerns that were unanswered ?

There are two questions to resolve.  The first is whether we should 
continue with the current direction (line-based protocol) or whether we 
should switch to an RPC.  The second question is which RPC we should use.

I'm not at all convinced that we should switch to an RPC mechanism in 
the first place.  Perhaps someone could summarize the advantages of 
doing this because right now, I don't see many.

With respect to RPC choice, if we did go that route, I'd be very 
concerned about using jsonrpc verses a more well established rpc.  I 
would honestly prefer xml-rpc over jsonrpc.

One reason to choose an RPC is based on the adoption of it.  You want to 
use something that has a vibrant community with well established client 
libraries to make writing clients as easy as possible.  Without an 
active jsonrpc C library, it's hard to argue that jsonrpc has that.  
xml-rpc certainly does.

Regards,

Anthony Liguori