From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:42219) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UfW3h-0005GD-Im for qemu-devel@nongnu.org; Thu, 23 May 2013 10:00:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UfW3c-0008UE-IV for qemu-devel@nongnu.org; Thu, 23 May 2013 09:59:57 -0400 Received: from mx1.redhat.com ([209.132.183.28]:62393) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UfW3c-0008U6-7Y for qemu-devel@nongnu.org; Thu, 23 May 2013 09:59:52 -0400 Message-ID: <519E20B5.7030701@redhat.com> Date: Thu, 23 May 2013 07:59:17 -0600 From: Eric Blake MIME-Version: 1.0 References: <20130523084655.41fb8f63@redhat.com> In-Reply-To: <20130523084655.41fb8f63@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="----enig2OIEVFMHGSAVIGBHEKIKH" Subject: Re: [Qemu-devel] "Designing QMP APIs" at KVM Forum List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Luiz Capitulino Cc: Stefan Hajnoczi , qemu-devel , Michael Roth This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2OIEVFMHGSAVIGBHEKIKH Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 05/23/2013 06:46 AM, Luiz Capitulino wrote: > On Thu, 23 May 2013 13:51:22 +0200 > Stefan Hajnoczi wrote: >=20 >> With better QMP introspection on the horizon and work in various >> subsystems pushing QMP boundaries it would be useful to bring together= >> the latest best practices for designing QMP APIs. >> >> There are design rules for keeping QMP APIs extensible and for >> allowing clients to detect the presence of features. There is also >> QEMU-side infrastructure like event rate-limiting, which developers >> should make use of where appropriate. >> >> Is anyone willing to bring together the best practices and present >> them at KVM Forum this year? >=20 > I think this is a great idea and I vote for Eric to prepare a presentat= ion. > Eric is doing an exceptional work on QMP command review, he is also > experienced on the client side. Indeed, it looks like I have a good topic for presentation. Yes, I'll take on that task for the KVM forum. >=20 >> I think that could help set the standard for QMP APIs. A set of >> slides or wiki page can be a reference to developers that stops us >> working from first pricinples every time a new API is added. >=20 > I was working on a doc to be added to docs/. It wouldn't be anything > fancy, but I ended up not finishing it. Even if you post the draft, that might help spur some ideas. --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org ------enig2OIEVFMHGSAVIGBHEKIKH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJRniC1AAoJEKeha0olJ0NqzrgH/0zAXUqj69yRZfli82zvb/3t enZAjfotttIgIdCMQKfzwkhGEbbq4L9iVyAC8EyLHp8TgyA53w/OV9kF/2OVGqRa 1t6KntoVkUtGg0kwvck7feOeCuo1+/bQKH83m3oSwq3Nk+AEPzyC6BwinWcgOMjh fyp/4I3sE3gIpQhemrCj0rSAwwU7qnx4ZngHWd1PJ04qjjItxu+dnxaca29wrvi3 aOPilCXRoPOBi56WnN0b0pX5iOxzvSsFwt2Lo74ZN+QQpzwapTgYEpXUONEqPCIU KKFiHPNo15NOKm9PDeUCfz3XFWqwLl62byKPZVlaqraf3zlEFyRKWWz9zvItuKA= =y5Ii -----END PGP SIGNATURE----- ------enig2OIEVFMHGSAVIGBHEKIKH--