On Mon, 01 Mar 2010 08:59:38 +0100
Markus Armbruster wrote:
> Luiz Capitulino writes:
[...]
> >We didn't expose 'info', for example, because
> > having a command (or 'remote procedure') returning all sorts of possible
> > data is no good.
>
> Why? What's the f
Luiz Capitulino writes:
> On Wed, 24 Feb 2010 18:55:12 +0100
> Markus Armbruster wrote:
>
>> Why this is such a big job? There are two issues with a naive
>> conversion:
>>
>> * Error message degradation
[...]
>> * String argument with option syntax, i.e. NAME=VALUE,...
>>
>> QMP uses JSON
On Wed, 24 Feb 2010 18:55:12 +0100
Markus Armbruster wrote:
> Why this is such a big job? There are two issues with a naive
> conversion:
>
> * Error message degradation
>
> The error messages are worded for -device. They aren't so hot to
> begin with: we typically have many -device optio
Why this is such a big job? There are two issues with a naive
conversion:
* Error message degradation
The error messages are worded for -device. They aren't so hot to
begin with: we typically have many -device options, and to which one
a message applies is often not obvious.
Now, QMP w
