Re: [Qemu-devel] [PATCH] Support VNC PointerTypeChange psuedo-encoding

[Anthony Liguori <anthony@codemonkey.ws>]

Ramesh Dharan wrote:
> I implemented new client->server messages for the (1) and (2), and
>   

I should have read more carefully.  This means that you're not a 
compliant RFB server ATM.

I guess that means there isn't a point registering the pseudo-encodings 
you are currently using since you have to change the server/client 
anyway.  It's easier anyway since pseudo-encodings are supposed to be 
negative numbers and you're using positive numbers.

I'm happy to start looking at reimplementing your encodings using my 
pseudo-encoding range.  It should be real easy for ya'll to support 
these too.  I'll spend a little time in the next week enumerating these 
extensions and assigning proper values to them.

Do you have any documentation on your currently client messages?  Those 
aren't documented as part of the FFMPEG project.

Regards,

Anthony Liguori

> server->client pseudorectangle extensions for (3) and (4). We deal with (5)
> in a different way; our display multiplexing is handled at a higher level. We
> ignored (6) since our clients currently only talk to our servers.
>
> Looking at the linked site, it looks like you folks have already identified
> and are planning to deal with (2), possibly (5) (via some games with the
> display name?) and (6). I'd be particularly interested to hear more about
> plans for how to address (5), it would be great if off-the-shelf/3rd-party
> clients could talk to multiple VMs running on a host without needing to know
> and use a separate the port for each VM. 
>
> Our remote consoles/clients are heavily tied to our products and there aren't
> any real plans to divest them or make them more generally useful in the near
> future. However, that's likely to change someday, and anyway I'd be happy to
> provide feedback on, and implement support for these extensions so that e.g.
> a QEMU client could talk to a VMware instance, and in general get
> standardization to the point where it's possible to build a single remote
> client that could talk to the various VM implementations (QEMU, Xen, VMware,
> etc.). 
>
> --
> Ramesh
>
>
>
>