From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NZkze-0000FH-Ta
	for qemu-devel@nongnu.org; Tue, 26 Jan 2010 07:58:06 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NZkza-0000Ci-5Y
	for qemu-devel@nongnu.org; Tue, 26 Jan 2010 07:58:06 -0500
Received: from [199.232.76.173] (port=51730 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NZkzZ-0000Cb-NJ
	for qemu-devel@nongnu.org; Tue, 26 Jan 2010 07:58:01 -0500
Received: from mail2.shareable.org ([80.68.89.115]:48605)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <jamie@shareable.org>) id 1NZkzZ-0005h7-AC
	for qemu-devel@nongnu.org; Tue, 26 Jan 2010 07:58:01 -0500
Date: Tue, 26 Jan 2010 12:57:54 +0000
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] [RFC 00/11]: QMP feature negotiation support
Message-ID: <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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100126095325.23011823@doriath>
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: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel@nongnu.org, aliguori@us.ibm.com, Markus Armbruster <armbru@redhat.com>, avi@redhat.com

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.

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

-- Jamie