From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PATCH v1 0/3] Convert VNC server to QIOChannel
Date: Wed, 18 Nov 2015 18:52:57 +0000 [thread overview]
Message-ID: <1447872780-2229-1-git-send-email-berrange@redhat.com> (raw)
This is an update of patches previously shown in an RFC posting
RFC: https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg00829.html
This series depends on the previously posted series:
"[PATCH v3 0/9] Introduce I/O channels framework"
This short series converts the VNC server to use the new
QIOChannel framework. This removes all the websocket protocol
code from the VNC server and further simplifies the TLS
handling in the VNC server
The conversion has been tested against the virt-viewer/
remote-viewer programs in the various TLS modes, and also
against the noVNC proxy websockets client with and without
TLS support.
Daniel P. Berrange (3):
ui: convert VNC server to use QIOChannelSocket
ui: convert VNC server to use QIOChannelTLS
ui: convert VNC server to use QIOChannelWebsock
ui/vnc-auth-sasl.c | 57 ++++-
ui/vnc-auth-vencrypt.c | 93 +++-----
ui/vnc-jobs.c | 20 +-
ui/vnc-ws.c | 400 ++++++--------------------------
ui/vnc-ws.h | 71 +-----
ui/vnc.c | 608 ++++++++++++++++++++++---------------------------
ui/vnc.h | 31 ++-
7 files changed, 448 insertions(+), 832 deletions(-)
--
2.5.0
next reply other threads:[~2015-11-18 18:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 18:52 Daniel P. Berrange [this message]
2015-11-18 18:52 ` [Qemu-devel] [PATCH v1 1/3] ui: convert VNC server to use QIOChannelSocket Daniel P. Berrange
2015-11-18 18:52 ` [Qemu-devel] [PATCH v1 2/3] ui: convert VNC server to use QIOChannelTLS Daniel P. Berrange
2015-11-18 18:53 ` [Qemu-devel] [PATCH v1 3/3] ui: convert VNC server to use QIOChannelWebsock Daniel P. Berrange
2015-12-15 10:35 ` [Qemu-devel] [PATCH v1 0/3] Convert VNC server to QIOChannel Gerd Hoffmann
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=1447872780-2229-1-git-send-email-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).