From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MJWkF-0003Se-8X
	for qemu-devel@nongnu.org; Wed, 24 Jun 2009 13:58:51 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MJWkA-0003L5-9b
	for qemu-devel@nongnu.org; Wed, 24 Jun 2009 13:58:50 -0400
Received: from [199.232.76.173] (port=35822 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MJWk9-0003KY-G7
	for qemu-devel@nongnu.org; Wed, 24 Jun 2009 13:58:45 -0400
Received: from cerberus.snarc.org ([212.85.155.21]:46211)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <tab@snarc.org>) id 1MJWUx-0000ii-91
	for qemu-devel@nongnu.org; Wed, 24 Jun 2009 13:43:03 -0400
Date: Wed, 24 Jun 2009 18:39:15 +0100
From: Vincent Hanquez <tab@snarc.org>
Subject: Re: [Qemu-devel] [PATCH 01/11] QMP: Introduce specification file
Message-ID: <20090624173915.GA16973@snarc.org>
References: <4A40FFB0.2070905@redhat.com> <4A411FC5.7050701@us.ibm.com>
	<4A412339.5000109@redhat.com> <4A412659.1080803@us.ibm.com>
	<20090623220204.GA5612@snarc.org> <4A415C30.7030301@us.ibm.com>
	<20090624010108.GA6537@snarc.org>
	<4A42200C.6060600@codemonkey.ws> <4A422592.2000307@redhat.com>
	<20090624162207.GD14121@shareable.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090624162207.GD14121@shareable.org>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Jamie Lokier <jamie@shareable.org>
Cc: ehabkost@redhat.com, jan.kiszka@siemens.com, dlaor@redhat.com, qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>, Avi Kivity <avi@redhat.com>

On Wed, Jun 24, 2009 at 05:22:07PM +0100, Jamie Lokier wrote:
> You can code a minimal XML parser in straight C quite easily, if it's
> a restricted subset.

even the restricted subset is not as straighforward as a json parser. and
usually using a subset means you can't interact correctly with the one that
does the full spec.

> XML and JSON both have the same ugly problem with binary data: they
> can't carry it.  It's usually base64 encoded.  Then again the QEMU
> monitor is no better this respect :-)

JSon ***DOES*** do binary data.

C String "abc\0\xff" -> Json String "abc\0000\00ff"

-- 
Vincent