From: Peter Lieven <pl@dlh.net>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] VNC encoding ZLibHex?
Date: Tue, 18 May 2010 14:01:05 +0200 [thread overview]
Message-ID: <4BF28181.1010701@dlh.net> (raw)
In-Reply-To: <AANLkTik5ZseAP8bhwR-zAX2ixOmjJKRQFacjWe7aYStj@mail.gmail.com>
is there any standard tests that can be run for comparing
different encodings? i am not familiar whit that unfortunately.
br,
peter
Corentin Chary wrote:
> The best way to know it would be to setup a vnc server with zlibhex
> support (libvncserver and ultravnc seems to support that encoding) and
> get some numbers (you can choose the prefered encoding with most of
> the vnc clients).
>
>
next prev parent reply other threads:[~2010-05-18 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 10:15 [Qemu-devel] VNC encoding ZLibHex? Peter Lieven
2010-05-18 11:37 ` Corentin Chary
2010-05-18 12:01 ` Peter Lieven [this message]
2010-05-18 12:16 ` Corentin Chary
2010-05-18 13:44 ` Anthony Liguori
2010-05-18 13:47 ` Peter Lieven
2010-05-18 13:56 ` Anthony Liguori
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=4BF28181.1010701@dlh.net \
--to=pl@dlh.net \
--cc=corentin.chary@gmail.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).