On 06/18/2010 03:59 PM, Markus Armbruster wrote:
The code is pretty confused about format vs. protocol, and so are we.
Let's try to figure them out.
From cruising altitude, all this format, protocol, stacking business
doesn't matter. We provide a bunch of arguments, and get an image.
If you look more closely, providing that image involves sub-tasks. One
is to haul bits. Another one is to translate between bits in different
formats.
Working hypothesis:
* A protocol hauls image bits. Examples: file, host_device, nbd.
* A format translates image formats. Examples: raw, qcow2.
Is there a reason to make the distinction? Is there a reason to expose
the distinction to the user?
--
error compiling committee.c: too many arguments to function
