From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MJXn0-0000wT-Rd for qemu-devel@nongnu.org; Wed, 24 Jun 2009 15:05:46 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MJXmw-0000rt-3d for qemu-devel@nongnu.org; Wed, 24 Jun 2009 15:05:46 -0400 Received: from [199.232.76.173] (port=40118 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MJXmv-0000rm-VJ for qemu-devel@nongnu.org; Wed, 24 Jun 2009 15:05:42 -0400 Received: from mx20.gnu.org ([199.232.41.8]:26388) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MJXmv-0003bL-9i for qemu-devel@nongnu.org; Wed, 24 Jun 2009 15:05:41 -0400 Received: from mail2.shareable.org ([80.68.89.115]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MJXmu-0005Zi-Mm for qemu-devel@nongnu.org; Wed, 24 Jun 2009 15:05:40 -0400 Date: Wed, 24 Jun 2009 20:05:39 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] [PATCH 01/11] QMP: Introduce specification file Message-ID: <20090624190539.GR14121@shareable.org> References: <4A40FFB0.2070905@redhat.com> <4A411FC5.7050701@us.ibm.com> <4A412339.5000109@redhat.com> <4A412659.1080803@us.ibm.com> <20090623220204.GA5612@snarc.org> <4A415C30.7030301@us.ibm.com> <20090624010108.GA6537@snarc.org> <4A42200C.6060600@codemonkey.ws> <5b31733c0906240857g546316e0pd92fee9afe6115fa@mail.gmail.com> <4A4252DD.70300@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A4252DD.70300@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: ehabkost@redhat.com, jan.kiszka@siemens.com, dlaor@redhat.com, qemu-devel@nongnu.org, Luiz Capitulino , Filip Navara , Vincent Hanquez Avi Kivity wrote: > On 06/24/2009 06:57 PM, Filip Navara wrote: > >Given the fact that we practically have the library for XDR it would > >be very easy to build Sun RPC server on top of it. So my vote is for > >SunRPC. > > > > My experience with SunRPC (NFS) has been pretty bad. It may have been > due to implementation details, not to the spec itself, but it definitely > left a bad taste in my mouth. Also, I don't see a SunRPC implementation > for Python, which (along with similar languages) is an ideal platform > for controlling qemu. I'd rather have something more modern. SunRPC works, and it's fine if you always access it through utilities, like say a C command-line client. Hiding the SunRPC aspect :-) It's pretty fast too, so good for things like network filesystems. But it's a real pain to use from scripts if you don't have a pre-built utility which implements all application RPC functions already. The basic problem is needing to create and compile C code - for all clients as well as the server - each time an RPC function is added or changed. QEMU's monitor is already much easier to use than that. When a new monitor command is added, you can use it from scripts as trivial one-liner text commands, assuming you already have a way to connect to the monitor. -- Jamie