From: Luiz Capitulino <lcapitulino@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 5/7] QMP: Update spec file
Date: Fri, 18 Dec 2009 15:55:44 -0200 [thread overview]
Message-ID: <20091218155544.2e2c671b@doriath> (raw)
In-Reply-To: <m3skb89p1n.fsf@crossbow.pond.sub.org>
On Fri, 18 Dec 2009 18:20:52 +0100
Markus Armbruster <armbru@redhat.com> wrote:
> Luiz Capitulino <lcapitulino@redhat.com> writes:
>
> [...]
> > -4. Notes to Client implementors
> > --------------------------------
> > +4. Compatibility Considerations
> > +--------------------------------
> >
> > -4.1 It is recommended to always start the Server in pause mode, thus the
> > - Client is able to perform any setup procedure without the risk of
> > - race conditions and related problems
> > +In order to achieve maximum compatibility between versions, the following
> > +changes are forbidden in newer versions of the Server:
> >
> > -4.2 It is recommended to always check the capabilities json-array, issued
> > - with the greeting message, at connection time
> > +- Removal of commands
> > +- Removal of command arguments
> > +- Addition of extra mandatory arguments for commands
> > +- Modification of arguments types
> > +- Modification of arguments, commands, events or error names
> > +- Modification of arguments in replies, events or errors
>
> While I think these promises are appropriate for a mature version of the
> protocol, I do not think we should make them for 0.12.
>
> We've just dreamed up version 0.1 of the protocol. It hasn't been used
> in anger. Yes, we put some serious thought in it, and we even have
> prototype code using it in libvirt, but let's face it, we're not
> infallible: we *will* have to evolve stuff.
While I agree with your arguments, I think this will happen to any
QMP version or any stable protocol/API.
You have the point that QMP is immature at this point, but:
1. Given the current Monitor design, if you want QMP to be perfect to be
useful then we're going to have it around QEMU version 10.0
2. I don't think we're going to get any serious user until we
declare it stable
next prev parent reply other threads:[~2009-12-18 17:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 15:24 [Qemu-devel] [FOR 0.12 0/7]: More QMP related fixes Luiz Capitulino
2009-12-18 15:24 ` [Qemu-devel] [PATCH 1/7] QMP: Only handle converted commands Luiz Capitulino
2009-12-18 15:25 ` [Qemu-devel] [PATCH 2/7] QMP: Return an empty dict by default Luiz Capitulino
2009-12-18 15:25 ` [Qemu-devel] [PATCH 3/7] QMP: Assure that returned data is a QDict Luiz Capitulino
2009-12-21 19:21 ` Nathan Baum
2009-12-22 3:06 ` Luiz Capitulino
2009-12-18 15:25 ` [Qemu-devel] [PATCH 4/7] QMP: Update README file Luiz Capitulino
2009-12-18 15:25 ` [Qemu-devel] [PATCH 5/7] QMP: Update spec file Luiz Capitulino
2009-12-18 17:20 ` Markus Armbruster
2009-12-18 17:44 ` Anthony Liguori
2009-12-18 17:48 ` Luiz Capitulino
2009-12-18 18:06 ` Markus Armbruster
2009-12-18 18:08 ` Luiz Capitulino
2009-12-18 17:55 ` Luiz Capitulino [this message]
2009-12-18 18:38 ` Markus Armbruster
2009-12-18 15:25 ` [Qemu-devel] [PATCH 6/7] monitor: Introduce 'M' argument type Luiz Capitulino
2009-12-18 15:25 ` [Qemu-devel] [PATCH 7/7] monitor: do_balloon(): Use " Luiz Capitulino
2009-12-18 17:25 ` [Qemu-devel] [FOR 0.12 0/7]: More QMP related fixes Markus Armbruster
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=20091218155544.2e2c671b@doriath \
--to=lcapitulino@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@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 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).