From: Tim Hardeck <thardeck@suse.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
github@martintribe.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] vnc: added initial websockets support
Date: Mon, 19 Nov 2012 11:09:21 +0100 [thread overview]
Message-ID: <50AA0551.6060006@suse.de> (raw)
In-Reply-To: <50A9F452.1030706@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
On 11/19/2012 09:56 AM, Gerd Hoffmann wrote:
> On 11/19/12 00:29, Tim Hardeck wrote:
>> 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?
>
> -vnc :0,websock=$portnr ?
This sounds resonable although maybe the websockets port could just
always be display + 1 so there is no need to parse a port.
Regards
Tim
--
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/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2012-11-19 10:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 15:13 [Qemu-devel] [PATCH] vnc: added initial websockets support Tim Hardeck
2012-11-16 15:13 ` Tim Hardeck
2012-11-18 9:31 ` Stefan Hajnoczi
2012-11-18 23:29 ` Tim Hardeck
2012-11-19 8:56 ` Gerd Hoffmann
2012-11-19 10:09 ` Tim Hardeck [this message]
2012-11-19 9:07 ` Stefan Hajnoczi
2012-11-19 10:00 ` Tim Hardeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50AA0551.6060006@suse.de \
--to=thardeck@suse.de \
--cc=github@martintribe.org \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.