From: Luiz Capitulino <lcapitulino@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: aliguori@us.ibm.com, dlaor@redhat.com, qemu-devel@nongnu.org,
avi@redhat.com
Subject: Re: [Qemu-devel] QMP forward compatibility support
Date: Tue, 12 Jan 2010 10:19:13 -0200 [thread overview]
Message-ID: <20100112101913.2664c795@doriath> (raw)
In-Reply-To: <m3my0j7n6c.fsf@blackfin.pond.sub.org>
On Tue, 12 Jan 2010 09:16:43 +0100
Markus Armbruster <armbru@redhat.com> wrote:
> >> Now, if everything is disabled by default and qemu might be running
> >> already, do we really need to have a handshake?
> >>
> >
> > I think it's valuable to have a discrete period of time when no
> > commands have been executed where features can be enabled. It
> > simplifies some nasty edge conditions regarding enabling features
> > while there are outstanding commands in flight.
>
> That's exactly why I lobbied for feature negotiation in the initial
> handshake, i.e. client connects, server sends greeting with features,
> client sends features it wants enabled, and only then we enter the
> normal command loop. Protocol that don't have that tend to get it
> retrofitted when they evolve.
>
> Let's do it now, before backward compatibility concerns force us to do
> it in an ugly way.
Yes, it was good to bring out the issue after all.
Please, review the design I'm proposing in my reply to Anthony.
next prev parent reply other threads:[~2010-01-12 12:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 18:34 [Qemu-devel] QMP forward compatibility support Luiz Capitulino
2010-01-11 18:57 ` Anthony Liguori
2010-01-11 19:49 ` Daniel P. Berrange
2010-01-12 0:04 ` Luiz Capitulino
2010-01-12 0:24 ` Anthony Liguori
2010-01-12 8:16 ` Markus Armbruster
2010-01-12 12:19 ` Luiz Capitulino [this message]
2010-01-12 12:11 ` Luiz Capitulino
2010-01-13 16:53 ` Markus Armbruster
2010-01-13 17:06 ` Luiz Capitulino
2010-01-13 17:38 ` Markus Armbruster
2010-01-13 17:43 ` Luiz Capitulino
2010-01-14 0:01 ` Jamie Lokier
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=20100112101913.2664c795@doriath \
--to=lcapitulino@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=avi@redhat.com \
--cc=dlaor@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).