From: Anthony Liguori <anthony@codemonkey.ws>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Eric Blake <eblake@redhat.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC/RFA PATCH] qapi: detect extra members inside structs
Date: Tue, 20 Mar 2012 14:33:31 -0500 [thread overview]
Message-ID: <4F68DB8B.40106@codemonkey.ws> (raw)
In-Reply-To: <20120320091550.35959dc5@doriath.home>
On 03/20/2012 07:15 AM, Luiz Capitulino wrote:
>> So let's work through a few examples. Today, you have to maintain a list of
>> commands returned from query-commands and check for set membership:
>>
>> if 'query-netdev2' in commands:
>> qmp.query_netdev2(foo)
>> else:
>> qmp.query_netdev()
>>
>> Pretty simple. If we have a schema representation, we'll need to be able to
>> check for arguments.
>
> Aren't we going to have the schema representation anyway? Or if we go for the
> way above we are not going to have it?
We have it, and we should expose it, but we should not IMHO require deep schema
introspection in order for a client to make use of new functionality.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2012-03-20 19:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 19:29 [Qemu-devel] [RFC/RFA PATCH] qapi: detect extra members inside structs Paolo Bonzini
2012-03-19 19:34 ` Anthony Liguori
2012-03-19 19:51 ` Paolo Bonzini
2012-03-19 19:56 ` Anthony Liguori
2012-03-19 20:22 ` Eric Blake
2012-03-19 20:30 ` Anthony Liguori
2012-03-19 20:43 ` Luiz Capitulino
2012-03-19 22:29 ` Michael Roth
2012-03-19 22:38 ` Anthony Liguori
2012-03-19 23:45 ` Michael Roth
2012-03-20 0:49 ` Anthony Liguori
2012-03-20 12:15 ` Luiz Capitulino
2012-03-20 19:33 ` Anthony Liguori [this message]
2012-03-20 17:31 ` Paolo Bonzini
2012-03-20 0:28 ` Michael Roth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F68DB8B.40106@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=eblake@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.