From: Anthony Liguori <anthony@codemonkey.ws>
To: Peter Lieven <pl@dlh.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] VNC encoding ZLibHex?
Date: Tue, 18 May 2010 08:44:27 -0500 [thread overview]
Message-ID: <4BF299BB.8020806@codemonkey.ws> (raw)
In-Reply-To: <4BF268B5.6080708@dlh.net>
On 05/18/2010 05:15 AM, Peter Lieven wrote:
> Hi,
>
> has someone enough background to say if it was worth implementing
> ZLibHex encoding
> to qemu/kvm?
The way I look at it, hextile is capable of a 16x16 tile that can be
raw, filled, or can contain colored subrects.
Tight allows arbitrary tile size, can be raw, filled, or paletted.
Paletted is going to be a pretty close approximation to colored subrects
(probably superior). Since Tight is compressed, the result should be
that Tight always does better than compressed hextile.
Not to mention the fact that ZLibHex is not supported very well across
clients.
Regards,
Anthony Liguori
> If yes, I would go for that.
>
> BR,
> Peter
>
>
next prev parent reply other threads:[~2010-05-18 13:44 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
2010-05-18 12:16 ` Corentin Chary
2010-05-18 13:44 ` Anthony Liguori [this message]
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=4BF299BB.8020806@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=pl@dlh.net \
--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).