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
