From: Avi Kivity <avi@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Christoph Hellwig <chellwig@redhat.com>,
qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] Re: RFC: blockdev_add & friends, brief rationale, QMP docs
Date: Sun, 06 Jun 2010 11:23:40 +0300 [thread overview]
Message-ID: <4C0B5B0C.2090403@redhat.com> (raw)
In-Reply-To: <m3aarayjbn.fsf@blackfin.pond.sub.org>
On 06/04/2010 05:16 PM, Markus Armbruster wrote:
> - "protocol": json-array of json-object
> Each element object has a member "name"
> - Possible values: "file", "nbd", ...
> Additional members depend on the value of "name".
> For "name" = "file":
> - "file": file name (json-string)
> For "name" = "nbd":
> - "domain": address family (json-string, optional)
> - Possible values: "inet" (default), "unix"
> - "file": file name (json-string), only with "domain" = "unix"
> - "host": host name (json-string), only with "domain" = "inet"
> - "port": port (json-int), only with "domain" = "inet"
> ...
>
>
This loses the nesting that protocols have. I'd like to see the each
nested protocol as member of the parent protocol. Besides the lovely }
} }s in the json representation, this allows us to have more complicated
protocols, for example a mirror protocol that has two child protocol
each specifying a different backing store.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-06-06 8:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 18:21 [Qemu-devel] RFC: blockdev_add & friends, brief rationale, QMP docs Markus Armbruster
2010-05-28 19:13 ` [Qemu-devel] " Kevin Wolf
2010-05-28 19:17 ` Anthony Liguori
2010-05-28 19:24 ` Luiz Capitulino
2010-05-30 9:11 ` Avi Kivity
2010-05-31 11:05 ` Markus Armbruster
2010-05-31 13:48 ` Luiz Capitulino
2010-05-31 14:04 ` Kevin Wolf
2010-05-30 9:09 ` Avi Kivity
2010-05-31 10:54 ` Markus Armbruster
2010-05-31 11:23 ` Avi Kivity
2010-05-31 11:50 ` Markus Armbruster
2010-06-04 14:16 ` Markus Armbruster
2010-06-04 14:32 ` Kevin Wolf
2010-06-04 15:53 ` Markus Armbruster
2010-06-04 16:20 ` Kevin Wolf
2010-06-06 8:23 ` Avi Kivity [this message]
2010-06-08 9:41 ` 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=4C0B5B0C.2090403@redhat.com \
--to=avi@redhat.com \
--cc=armbru@redhat.com \
--cc=chellwig@redhat.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@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).