From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NZlja-0000un-Ql
	for qemu-devel@nongnu.org; Tue, 26 Jan 2010 08:45:34 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NZljV-0000ne-UZ
	for qemu-devel@nongnu.org; Tue, 26 Jan 2010 08:45:34 -0500
Received: from [199.232.76.173] (port=36229 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NZljV-0000nK-M1
	for qemu-devel@nongnu.org; Tue, 26 Jan 2010 08:45:29 -0500
Received: from mx1.redhat.com ([209.132.183.28]:59586)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <lcapitulino@redhat.com>) id 1NZljV-0003ly-66
	for qemu-devel@nongnu.org; Tue, 26 Jan 2010 08:45:29 -0500
Date: Tue, 26 Jan 2010 11:45:21 -0200
From: Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [RFC 00/11]: QMP feature negotiation support
Message-ID: <20100126114521.149a2f78@doriath>
In-Reply-To: <20100126125754.GA9362@shareable.org>
References: <1264108180-3666-1-git-send-email-lcapitulino@redhat.com>
	<4B59E7C4.2050201@codemonkey.ws>
	<m33a1utfsr.fsf@blackfin.pond.sub.org>
	<20100126095325.23011823@doriath>
	<20100126125754.GA9362@shareable.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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: qemu-devel@nongnu.org, aliguori@us.ibm.com, Markus Armbruster <armbru@redhat.com>, avi@redhat.com

On Tue, 26 Jan 2010 12:57:54 +0000
Jamie Lokier <jamie@shareable.org> wrote:

> Luiz Capitulino wrote:
> > capability_enable [ "foo", "bar" ]
> > 
> >  Now, only one command is not terrible difficult, but we would
> > have to accept an array of objects, like:
> > 
> > [ { "name": "foo", "enabled": true }, { "name": "bar", "enabled": true } ]
> 
> That looks like XML-itis.

 This is valid json, we already output data in this format and will
likely accept it in other commands.

> Why not { "foo": true, "bar": true }?

 Possible, but if we use a dict then I would prefer the previous format,
because it can be extended in a compatible way (while a single list and
yours don't).