Re: [Qemu-devel] [5076] VNC: Support for ExtendedKeyEvent client message

[Anthony Liguori <anthony@codemonkey.ws>]

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