qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] Re: RFC: blockdev_add & friends, brief rationale, QMP docs


From: Avi Kivity
Subject: [Qemu-devel] Re: RFC: blockdev_add & friends, brief rationale, QMP docs
Date: Sun, 06 Jun 2010 11:23:40 +0300
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-3.fc13 Thunderbird/3.0.4

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]