From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KYoAq-0003V2-OC
	for qemu-devel@nongnu.org; Thu, 28 Aug 2008 16:32:56 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KYoAp-0003TH-1P
	for qemu-devel@nongnu.org; Thu, 28 Aug 2008 16:32:56 -0400
Received: from [199.232.76.173] (port=59883 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KYoAo-0003T3-Qg
	for qemu-devel@nongnu.org; Thu, 28 Aug 2008 16:32:54 -0400
Received: from an-out-0708.google.com ([209.85.132.249]:14211)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1KYoAo-0003R5-E7
	for qemu-devel@nongnu.org; Thu, 28 Aug 2008 16:32:54 -0400
Received: by an-out-0708.google.com with SMTP id d18so88488and.130
	for <qemu-devel@nongnu.org>; Thu, 28 Aug 2008 13:32:51 -0700 (PDT)
Message-ID: <48B70B43.7050302@codemonkey.ws>
Date: Thu, 28 Aug 2008 15:32:03 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [5076] VNC: Support for ExtendedKeyEvent client
	message
References: <E1KX2WA-0006Wo-4R@cvs.savannah.gnu.org>
	<74C8A544-F282-43CF-B33F-1E8972658190@suse.de>
In-Reply-To: <74C8A544-F282-43CF-B33F-1E8972658190@suse.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org

Alexander Graf wrote:
>
> On Aug 24, 2008, at 1:27 AM, Anthony Liguori wrote:
>
> How do you standardize VNC protocol extensions? I've been wondering 
> about this for quite a while as I've got two VNC patches in my queue 
> myself.
> The first one allows the client to send a keyboard layout (so the -k 
> option could be changed dynamically, mostly because the Java client 
> can't find symcodes).

There's no need.  Simply do the conversion from Java keysyms => PC scan 
code using the same conversion routines that QEMU use within your Java 
client.

> The other one implements PNG compression for Tight.

I doubt you'll see a benefit from this.  PNG compression is paletted and 
compressed (just like GIF).  Tight already supports paletting and 
compression (using zlib).  Algorithmically, you're not going to get any 
benefit.

The reason tight supports jpeg compression is that jpeg is a lossy 
compression algorithm.  This is why jpeg compression can do better than 
the normal Tight algorithm (although you lose quality).

Regards,

Anthony Liguori

> I'd really love to have both of them standardized, but where do I need 
> to apply for an identifier ID?
>
> [...snip...]
>
> Thanks,
>
> Alex