qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [5076] VNC: Support for ExtendedKeyEvent client message
Date: Thu, 28 Aug 2008 16:47:11 -0500	[thread overview]
Message-ID: <48B71CDF.6030806@codemonkey.ws> (raw)
In-Reply-To: <28A4FF84-9A3A-4A60-A67B-3533530A728D@df.lth.se>

Christian Brunschen wrote:
>
>>
>> I doubt you'll see a benefit from this.  PNG compression is paletted 
>> and compressed (just like GIF).
>
> PNG does more than that. PNG supports full colour (up to 16 bits per 
> colour component) including a full alpha channel, and has various 
> filters that are applied to the image data to improve compression. Not 
> to mention PNG is much more than GIF.

Tight also has various filters to improve the compression.  The VNC 
protocol won't support 16-bit color components or an alpha channel so 
this isn't an advantage.

> As an aside - is the Tight protocol documented somewhere? In actual 
> documentation rather than source code, I mean?

Just the source code.  Although there's a big comment block that 
describes it as well as the rest of the VNC protocol docs do.

Regards,

Anthony Liguori

      reply	other threads:[~2008-08-28 21:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-23 23:27 [Qemu-devel] [5076] VNC: Support for ExtendedKeyEvent client message Anthony Liguori
2008-08-27 10:02 ` Alexander Graf
2008-08-27 10:31   ` Daniel P. Berrange
2008-08-28 20:32   ` Anthony Liguori
2008-08-28 20:44     ` Christian Brunschen
2008-08-28 21:47       ` Anthony Liguori [this message]

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=48B71CDF.6030806@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=agraf@suse.de \
    --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).