[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Ramesh Dharan
Subject: RE: [Qemu-devel] [PATCH] Support VNC PointerTypeChange psuedo-encoding
Date: Thu, 29 Mar 2007 20:26:41 -0700

> 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 SetServerEncodings message)?

It just drops it ;=0. Yeah, you're right, there's no good way. 

> I think it's easier to just add something to the psuedo-encoding to 
> allow client messages that make sense to disable to be disabled on a 
> case-by-case basis.

Fair enough. In any case, I haven't encountered a situation before where the
server wanted to remove support for a client message. The only one I've
encountered is where the client wants to indicate changed conditions on its
end (e.g. failure to map the shared framebuffer).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]