|
From: | Avi Kivity |
Subject: | Re: [Qemu-devel] [PATCH 01/11] QMP: Introduce specification file |
Date: | Wed, 24 Jun 2009 19:25:46 +0300 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Lightning/1.0pre Thunderbird/3.0b2 |
On 06/24/2009 07:22 PM, Jamie Lokier wrote:
Avi Kivity wrote: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.I agree xml-rpc is a more rational choice than jsonrpc, but I cannot find it in my heart to say something nice about xml. Additionally, XML parsers are pretty heavy.I'm not defending XML here, but: You can code a minimal XML parser in straight C quite easily,
One of the points of using an existing RPC implementation is not to have to code it up.
if it's a restricted subset.
You can't control what's coming in from the other side. -- error compiling committee.c: too many arguments to function
[Prev in Thread] | Current Thread | [Next in Thread] |