Thanks Erik and Gerd for you feedback...
I will rebase the changes consider the opinions...
I agree about VncInfo2... because some structures are ready to use,
including websocket.
Without adding new fields or other changes.
Julio Cesar Faracco
2015-10-19 6:17 GMT-02:00 Gerd Hoffmann :
> Hi,
Hi,
> diff --git a/qapi-schema.json b/qapi-schema.json
> index a386605..e97f78f 100644
> --- a/qapi-schema.json
> +++ b/qapi-schema.json
> @@ -916,7 +916,8 @@
> { 'struct': 'VncInfo',
>'data': {'enabled': 'bool', '*host': 'str',
> '*family': 'NetworkAddressFamily',
> -
On 10/16/2015 10:37 AM, Julio Faracco wrote:
> When the user setup a vnc server to QEMU using the argument "-vnc
> 0.0.0.0:0,websocket=5701" for example, he cannot get information about which
> websocket port VNC is running. The command "info vnc" shows only details about
> the main VNC server and
When the user setup a vnc server to QEMU using the argument "-vnc
0.0.0.0:0,websocket=5701" for example, he cannot get information about which
websocket port VNC is running. The command "info vnc" shows only details about
the main VNC server and the clients. You can confirm that a websocket service
