Hi Anthony, sorry for the delayed response to your delayed response.
I actually haven't been working much on the remote display stuff in a while,
though it's something I'm hoping to get involved with again time permitting.
I'm cc'ing Dustin Byford and Johnson Liu, VMware engineers who handle a
Ramesh Dharan wrote:
Anthony, I have a detailed response to your earlier e-mail but I wanted to
handle this discussion separately.
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
Ramesh Dharan wrote:
Hi Anthony, sorry for the delayed response to your delayed response.
No problem.
I actually haven't been working much on the remote display stuff in a while,
though it's something I'm hoping to get involved with again time permitting.
I'm cc'ing Dustin Byford and
The proper way to use new client message types (which is now
described
in the RFB spec) is to advertise a new pseudo-encoding for
that client
message type and wait for the server to send the
pseudo-encoding back to
the client. That lets the client know that it is safe to use the new
Ramesh Dharan wrote:
The proper way to use new client message types (which is now
described
in the RFB spec) is to advertise a new pseudo-encoding for
that client
message type and wait for the server to send the
pseudo-encoding back to
the client. That lets the client know that it is safe
To do it in general? Yeah, I don't think there's a solution. Of
course, a SetServerEncodings would introduce a race. What does the
server do if it receives one of the new special client messages after
sending the SetServerEncodings message (but before the client
receives
the
[EMAIL PROTECTED] wrote:
This extension is documented at
http://tocm.wikidot.com/pointertypechange
VMware has a very similar extension for their remote console. I
believe
that Ramesh Dharan (whom I've CCed) at some point implemented it in one
or more open source clients. Perhaps some
Ramesh Dharan wrote:
[EMAIL PROTECTED] wrote:
This extension is documented at
http://tocm.wikidot.com/pointertypechange
VMware has a very similar extension for their remote console. I
believe
that Ramesh Dharan (whom I've CCed) at some point implemented it in one
or more open
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
The following patch adds support to the VNC server for the
PointerTypeChange. This is a new encoding I've defined specifically for
virtualization. It allows a VNC client to support a server that has a
relative mouse (such as a PS/2 mouse in QEMU). If you're familiar with
the mouse being
10 matches
Mail list logo
