From: Luiz Capitulino <lcapitulino@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: "Benoît Canet" <benoit.canet@irqsave.net>,
kwolf@redhat.com, "Markus Armbruster" <armbru@redhat.com>,
stefanha@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] How to introduce bs->node_name ?
Date: Fri, 1 Nov 2013 11:12:35 -0400 [thread overview]
Message-ID: <20131101111235.381c8373@redhat.com> (raw)
In-Reply-To: <5273C1C8.4010601@redhat.com>
On Fri, 01 Nov 2013 08:59:20 -0600
Eric Blake <eblake@redhat.com> wrote:
> On 11/01/2013 08:51 AM, Luiz Capitulino wrote:
> > On Wed, 30 Oct 2013 13:25:35 -0600
> > Eric Blake <eblake@redhat.com> wrote:
> >
> >> On 10/30/2013 07:49 AM, Markus Armbruster wrote:
> >>
> >>>
> >>> The first proposal is to add another parameter, say "id". Users can
> >>> then refer either to an arbitrary BDS by "id", or (for backward
> >>> compatibility) to the root BDS by "device". When the code sees
> >>> "device", it'll look up the BB, then fetch its root BDS.
> >>>
> >>> CON: Existing parameter "device" becomes compatibility cruft.
> >>>
> >>> PRO: Clean and obvious semantics (in my opinion).
> >>
> >> I like this one as well.
> >
> > Does this proposal makes "device" optional for existing commands? If it
> > does then I'm afraid it breaks compatibility because if you don't
> > specify a device you'll get an error today.
>
> Changing from error to success is not backwards-incompatible. Old
> applications will ALWAYS supply device (because it used to be
> mandatory). That is, a management application that was intentionally
> omitting 'device' and expecting an error is so unlikely to exist that we
> can consider such a management app as buggy.
Doing such changes makes me nervous nevertheless. In my mind a stable
API doesn't change. Of course that there might exceptions, but 99.9%
of those exceptions should be bug fixes not deliberate API extensions.
A more compelling argument against it is the quality of the resulting
command. I'm sure it's going to be anything but a simple, clean API.
Anyways, let's wait for a concrete proposal to have more concrete
feedback.
next prev parent reply other threads:[~2013-11-01 15:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 15:40 [Qemu-devel] How to introduce bs->node_name ? Benoît Canet
2013-10-29 1:03 ` Fam Zheng
2013-10-30 13:49 ` Markus Armbruster
2013-10-30 19:25 ` Eric Blake
2013-11-01 14:51 ` Luiz Capitulino
2013-11-01 14:59 ` Eric Blake
2013-11-01 15:12 ` Luiz Capitulino [this message]
2013-11-04 11:13 ` Kevin Wolf
2013-11-04 13:51 ` Luiz Capitulino
2013-11-04 9:31 ` Stefan Hajnoczi
2013-11-04 9:48 ` Fam Zheng
2013-11-04 11:06 ` Kevin Wolf
2013-11-04 11:33 ` Fam Zheng
2013-11-07 18:50 ` Benoît Canet
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=20131101111235.381c8373@redhat.com \
--to=lcapitulino@redhat.com \
--cc=armbru@redhat.com \
--cc=benoit.canet@irqsave.net \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 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.