From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NuPeY-0005sA-RN for qemu-devel@nongnu.org; Wed, 24 Mar 2010 08:25:42 -0400 Received: from [140.186.70.92] (port=52801 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NuPeU-0005px-B9 for qemu-devel@nongnu.org; Wed, 24 Mar 2010 08:25:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NuPeQ-0004ny-Dm for qemu-devel@nongnu.org; Wed, 24 Mar 2010 08:25:38 -0400 Received: from mx20.gnu.org ([199.232.41.8]:40380) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NuPeQ-0004ns-AV for qemu-devel@nongnu.org; Wed, 24 Mar 2010 08:25:34 -0400 Received: from mail.codesourcery.com ([38.113.113.100]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NuPeP-0008JZ-Q8 for qemu-devel@nongnu.org; Wed, 24 Mar 2010 08:25:34 -0400 From: Paul Brook Subject: Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in libvirt Date: Wed, 24 Mar 2010 12:25:28 +0000 References: <4BA7C40C.2040505@codemonkey.ws> <4BA962F3.1020107@codemonkey.ws> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201003241225.30442.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: "libvir-list@redhat.com" , Markus Armbruster , Alexander Graf > I can't quite see what such a libqemu would buy us compared to straight > QMP. > > Talking QMP should be easy, provided you got a suitable JSON library. I agree. My undesranding is this was one of the large motivations behind using JSON: It's a common protocol that already has convenient bindings in most languages. If it's hard[1] for third parties to bind QMP to their favourite language/framework then IMHO we've done it wrong. Paul [1] Hard compared to any other sane RPC mechanism. Some languages make everything hard :-)