From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33333) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZXVXk-0005HU-Ii for qemu-devel@nongnu.org; Thu, 03 Sep 2015 10:31:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZXVXg-0005sW-Fp for qemu-devel@nongnu.org; Thu, 03 Sep 2015 10:31:12 -0400 Received: from mx1.redhat.com ([209.132.183.28]:17262) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZXVXg-0005sO-Ar for qemu-devel@nongnu.org; Thu, 03 Sep 2015 10:31:08 -0400 References: <1438703896-12553-1-git-send-email-armbru@redhat.com> <1438703896-12553-31-git-send-email-armbru@redhat.com> <20150901184026.18566.39890@loki> <55E5F898.6040304@redhat.com> <20150901202348.18566.60300@loki> <87io7t42t2.fsf@blackfin.pond.sub.org> <20150902162156.11972.58160@loki> <87r3mfyhty.fsf@blackfin.pond.sub.org> From: Eric Blake Message-ID: <55E859A5.9060807@redhat.com> Date: Thu, 3 Sep 2015 08:31:01 -0600 MIME-Version: 1.0 In-Reply-To: <87r3mfyhty.fsf@blackfin.pond.sub.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Ji0MkdMfou4sbrxH9IkqwKSIRERagnlD8" Subject: Re: [Qemu-devel] [PATCH RFC v3 30/32] qapi: New QMP command query-schema for QMP schema introspection List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster , Michael Roth Cc: kwolf@redhat.com, berto@igalia.com, qemu-devel@nongnu.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Ji0MkdMfou4sbrxH9IkqwKSIRERagnlD8 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 09/03/2015 03:26 AM, Markus Armbruster wrote: >> >> I think we need to be careful that these descriptions are not >> interpreted by clients as an alternative to the more-specific >> constraints in the QAPI schema though. 'query-schema' seems >> a bit misleading in that regard, it appears to be more like >> 'query-schema-encoding' in function. But not sure it's worth >> renaming or anything so long as the documentation is clear. >=20 > You have a point: "schema" can mean two related, yet different things. > There's the QAPI schema, and there's the QMP (the wire protocol) schema= =2E > QMP introspection is about the latter, not the former. >=20 > If we want to avoid the ambiguity, we could call the command > query-qmp-schema or something. >=20 > Renaming query-schema now might confuse people coming from my KVM Forum= > talk slightly, but if we can agree on a better name, let's do it. I'm okay if you want to use 'query-qmp-schema'; it's a bit longer, but more precise, and doesn't cause too much grief to change the name at this point in the game. --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --Ji0MkdMfou4sbrxH9IkqwKSIRERagnlD8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJV6FmlAAoJEKeha0olJ0NqGmkH/j7RIEJPVRK+cGKKmrkh0PYR 21aywROooi7DjglL56z4KCGrAGM5ieqpS0OZlqIPLlhdotADHwRk+o5mZWhEzVWB 271D0Fyp4kcLFfrUL2S8lrOMz6pArdHpfIVe4E8T5mCGcIgfDbRwhECuKssnMn/P vvITxvJEcs/Fbrw2iz+t9Nv5zNclfPd63DEG7Sx8yAC7LreIuPrSy0UL2vfj/6Z1 GoPegV2kp0Mc6nsvQuabTw/8ikNd/osAB78F6ktvIUMwwt6jSUcPx4VUJv235M1b DKec9WG/8+cvt1wMQ0/HjXMYSUD/VWajyBltfffHLx2MOZachs6mqvipq9o/76A= =2lb0 -----END PGP SIGNATURE----- --Ji0MkdMfou4sbrxH9IkqwKSIRERagnlD8--