Gerd Hoffmann writes:
> Hi,
>
>> > If the schema let us specify the enumeration values, we could avoid the
>> > mapping altogether.
>>
>> Ooh, cool thought: what if we allowed:
>>
>> { 'enum': 'Foo', 'data': [
>> { 'name': 'One', 'value': 1 },
>> { 'name': 'Two', 'value': 2 } ] }
>
> Look
On Fr, 2014-12-19 at 14:04 +0100, Markus Armbruster wrote:
> Gerd Hoffmann writes:
>
> > Add new query vnc qmp command, for the lack of better ideas just name it
> > "query-vnc2". Changes over query-vnc:
> >
> > * It returns a list of vnc servers, so multiple vnc server instances
> >are cov
Hi,
> > If the schema let us specify the enumeration values, we could avoid the
> > mapping altogether.
>
> Ooh, cool thought: what if we allowed:
>
> { 'enum': 'Foo', 'data': [
> { 'name': 'One', 'value': 1 },
> { 'name': 'Two', 'value': 2 } ] }
Looks nice. Where is the patch?
cheers,
> > Add new query vnc qmp command, for the lack of better ideas just name it
> > "query-vnc2". Changes over query-vnc:
> Call it query-vnc-servers?
Fine with me, done.
> Maybe just VncPrimaryAuth, since there's precedence for abbreviating
> authentication that way.
Done.
> > ##
> > +# @quer
On 12/19/2014 06:04 AM, Markus Armbruster wrote:
> Gerd Hoffmann writes:
>
>> Add new query vnc qmp command, for the lack of better ideas just name it
>> "query-vnc2". Changes over query-vnc:
>>
>> * It returns a list of vnc servers, so multiple vnc server instances
>>are covered.
>> * Eac
Gerd Hoffmann writes:
> Add new query vnc qmp command, for the lack of better ideas just name it
> "query-vnc2". Changes over query-vnc:
>
> * It returns a list of vnc servers, so multiple vnc server instances
>are covered.
> * Each vnc server returns a list of server sockets. Followup pa
Add new query vnc qmp command, for the lack of better ideas just name it
"query-vnc2". Changes over query-vnc:
* It returns a list of vnc servers, so multiple vnc server instances
are covered.
* Each vnc server returns a list of server sockets. Followup patch
will use that to also report
