qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] "Designing QMP APIs" at KVM Forum
Date: Thu, 23 May 2013 08:46:55 -0400	[thread overview]
Message-ID: <20130523084655.41fb8f63@redhat.com> (raw)
In-Reply-To: <CAJSP0QW_LqQAKkTxqRSyyBOAXyAmy3Bg0FBt-jVyUSe2B+p5sQ@mail.gmail.com>

On Thu, 23 May 2013 13:51:22 +0200
Stefan Hajnoczi <stefanha@gmail.com> wrote:

> 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 this is a great idea and I vote for Eric to prepare a presentation.
Eric is doing an exceptional work on QMP command review, he is also
experienced on the client side.

> 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.

I was working on a doc to be added to docs/. It wouldn't be anything
fancy, but I ended up not finishing it.

  reply	other threads:[~2013-05-23 12:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23 11:51 [Qemu-devel] "Designing QMP APIs" at KVM Forum Stefan Hajnoczi
2013-05-23 12:46 ` Luiz Capitulino [this message]
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=20130523084655.41fb8f63@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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).