From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nunb5-0003aC-KJ for qemu-devel@nongnu.org; Thu, 25 Mar 2010 09:59:43 -0400 Received: from [140.186.70.92] (port=43409 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nunb3-0003Yy-GW for qemu-devel@nongnu.org; Thu, 25 Mar 2010 09:59:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Nunb1-00014x-8h for qemu-devel@nongnu.org; Thu, 25 Mar 2010 09:59:41 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48134) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Nunb0-00014F-Vi for qemu-devel@nongnu.org; Thu, 25 Mar 2010 09:59:39 -0400 Date: Thu, 25 Mar 2010 13:59:22 +0000 From: "Daniel P. Berrange" Subject: Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in libvirt Message-ID: <20100325135922.GB10705@redhat.com> References: <4BA9A066.3070904@redhat.com> <20100324103643.GB624@redhat.com> <4BA9EC88.6000906@redhat.com> <20100324134250.38822113@redhat.com> <4BAA6CD9.6060001@redhat.com> <20100324171219.4365318b@redhat.com> <4BAA76EA.2060601@codemonkey.ws> <20100324182501.000b69a7@redhat.com> <4BAA86C2.4020701@codemonkey.ws> <4BAB1E21.8080009@snarc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BAB1E21.8080009@snarc.org> Reply-To: "Daniel P. Berrange" List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vincent Hanquez Cc: "libvir-list@redhat.com" , qemu-devel@nongnu.org, Luiz Capitulino , Paul Brook , Avi Kivity On Thu, Mar 25, 2010 at 08:26:09AM +0000, Vincent Hanquez wrote: > On 24/03/10 21:40, Anthony Liguori wrote: > >>If so, what C clients you expected beyond libvirt? > > > >Users want a C API. I don't agree that libvirt is the only C > >interface consumer out there. > > (I've seen this written too many times ...) > How do you know that ? did you do a poll or something where *actual* > users vote/tell ? > > From my point of view, i wouldn't want to write a high level management > toolstack in C, specially > since the API is well defined JSON which is easily available in all high > level language out there. It was pretty straightforward for libvirt to talk to the JSON protocol from C using the YAJL library, so I don't think it is all that much of a barrier for low level languages like C either. If we want to make life easy for app/library developers working against QEMU, then the far more important aspect is to guarentee stability of all the QEMU interfaces since that is where all the serious pain occurs over time. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|