Hi Stefan, thanks for your input but how should it be implemented?
I personally would like activating Websockets as a VNC option like: " -vnc :0 -vnc :1,websockets" I have already tested this locally and it does work but only for one protocol since QEMU does only interpret the last vnc option. So is allowing more than one VNC command line entry in combination with having more than one VNC thread for the same display worth working on or do you have something different in mind? Regards Tim On Sun, 2012-11-18 at 10:31 +0100, Stefan Hajnoczi wrote: > On Fri, Nov 16, 2012 at 4:13 PM, Tim Hardeck <thard...@suse.de> wrote: > > Websockets connections are recognized by waiting 500ms for a Websocket > > handshake. If no data is received a regular vnc connection is assumed. > > If this is not acceptable please suggest if Websockets should be activated > > by a new VNC option or by an additional console parameter on a different > > port. > > Perhaps it's better to speak Websockets on a different port. That way > no timer is required and we never fail to detect the correct protocol > to speak. > > Stefan -- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany T: +49 (0) 911 74053-0 F: +49 (0) 911 74053-483 http://www.suse.de/
signature.asc
Description: This is a digitally signed message part
