From: Stefan Hajnoczi <stefanha@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: [Qemu-devel] "Designing QMP APIs" at KVM Forum
Date: Thu, 23 May 2013 13:51:22 +0200 [thread overview]
Message-ID: <CAJSP0QW_LqQAKkTxqRSyyBOAXyAmy3Bg0FBt-jVyUSe2B+p5sQ@mail.gmail.com> (raw)
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?
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.
Stefan
next reply other threads:[~2013-05-23 12:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 11:51 Stefan Hajnoczi [this message]
2013-05-23 12:46 ` [Qemu-devel] "Designing QMP APIs" at KVM Forum Luiz Capitulino
2013-05-23 13:59 ` Eric Blake
2013-05-24 9:49 ` Stefan Hajnoczi
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=CAJSP0QW_LqQAKkTxqRSyyBOAXyAmy3Bg0FBt-jVyUSe2B+p5sQ@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=lcapitulino@redhat.com \
--cc=mdroth@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).