From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nuoes-0005Xz-3k for qemu-devel@nongnu.org; Thu, 25 Mar 2010 11:07:42 -0400 Received: from [140.186.70.92] (port=39222 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nuoep-0005XX-Gg for qemu-devel@nongnu.org; Thu, 25 Mar 2010 11:07:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Nuoen-0004eW-7Z for qemu-devel@nongnu.org; Thu, 25 Mar 2010 11:07:39 -0400 Received: from mx1.redhat.com ([209.132.183.28]:45308) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Nuoen-0004eK-09 for qemu-devel@nongnu.org; Thu, 25 Mar 2010 11:07:37 -0400 Date: Thu, 25 Mar 2010 15:07:20 +0000 From: "Daniel P. Berrange" Subject: Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in libvirt Message-ID: <20100325150720.GH10705@redhat.com> References: <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> <20100325135922.GB10705@redhat.com> <20100325145652.GA25506@snarc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100325145652.GA25506@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 02:56:52PM +0000, Vincent Hanquez wrote: > On Thu, Mar 25, 2010 at 01:59:22PM +0000, Daniel P. Berrange wrote: > > > 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. > > note, that it's not the talking JSON part that's difficult to do in C (it's > just midly annoying compare to a highlevel language), but all the other part of > a toolstack. Since there's no performance requirements, writing in C is just a > bit of a waste ot time, but that's up to the developpers to choose the tools he > wants, even if it's not the most appropriate one ;) > > > 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. > > if you're talking about the QMP interface then I agree with you. This need to > be back/forward compatible as much as possible and stable. > > the other interface (i.e. the user monitor) has no business beeing > backward-compatible though, since it should never be used to talk a RPC. I agree apps shouldn't use it for RPC, but admins using the interactive user monitor are just as deserving of stable commands & args. 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 :|