From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MJ8TS-0001rG-3i for qemu-devel@nongnu.org; Tue, 23 Jun 2009 12:03:54 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MJ8TN-0001n0-AG for qemu-devel@nongnu.org; Tue, 23 Jun 2009 12:03:53 -0400 Received: from [199.232.76.173] (port=56886 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MJ8TM-0001mX-OD for qemu-devel@nongnu.org; Tue, 23 Jun 2009 12:03:48 -0400 Received: from mx2.redhat.com ([66.187.237.31]:54718) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MJ8TM-0003AD-1n for qemu-devel@nongnu.org; Tue, 23 Jun 2009 12:03:48 -0400 Message-ID: <4A40FD1A.1040303@redhat.com> Date: Tue, 23 Jun 2009 19:04:42 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 01/11] QMP: Introduce specification file References: <20090623012811.53a62493@doriath> <20090623144521.GA614@snarc.org> <4A40FB11.8090100@redhat.com> <4A40FB26.2040702@us.ibm.com> In-Reply-To: <4A40FB26.2040702@us.ibm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: ehabkost@redhat.com, jan.kiszka@siemens.com, dlaor@redhat.com, qemu-devel@nongnu.org, Luiz Capitulino , Vincent Hanquez On 06/23/2009 06:56 PM, Anthony Liguori wrote: > Avi Kivity wrote: >> On 06/23/2009 05:45 PM, Vincent Hanquez wrote: >>> >>> At this point my personal suggestion would be jsonrpc: >>> >>> - it's easy to parse (even in C) >>> - it's text with markup >>> - easy to generate >>> - support utf-8 >>> - quoted string >>> - it's not ugly to read (compare to xml) >>> - can be embedded directly (no more library dependancy for qemu) in >>> the code >>> - lots of language have json library making the interaction with the >>> monitor >>> easy from the other side >> >> - supports passing structure >> - supports notifications >> - supports asynchronous commands >> >> seems quite nice. > > I'd rather not do json. > Why not? > As they stand, I think the current patch set is very close to being > mergable. I'd rather not go off on a new tangent. It fulfils all are requirements and more. There's a C implementation available. We can concentrate on the commands and ignore the plumbing. -- error compiling committee.c: too many arguments to function