qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Tim Hardeck <thardeck@suse.de>
Cc: github@martintribe.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] vnc: added initial websockets support
Date: Mon, 19 Nov 2012 10:07:00 +0100	[thread overview]
Message-ID: <20121119090700.GA18034@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1353281384.3623.38.camel@Thinktank.site>

On Mon, Nov 19, 2012 at 12:29:44AM +0100, 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?

I'm not familiar enough with the VNC code to suggest how to best
implement this.

One thing to think about is that Websockets is a transport.  Perhaps the
VNC code itself shouldn't speak it, instead generic QEMU socket code
should implement Websockets so that non-VNC components can also make use
of it in the future.

Stefan

  parent reply	other threads:[~2012-11-19  9:07 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
2012-11-19  9:07     ` Stefan Hajnoczi [this message]
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=20121119090700.GA18034@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=github@martintribe.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thardeck@suse.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).