| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] Re: [PATCH] qemu vnc updates
Daniel P. Berrange wrote:
On Tue, Feb 26, 2008 at 10:15:51AM -0600, Anthony Liguori wrote:
Stefano Stabellini wrote:
Hi all,
reading qemu code I realized that the qemu vnc server sometimes sends
framebuffer updates even if the client didn't request any.
This is not consistent with the RFB protocol spec and can break some
clients.
It's actually consistent with the RFB spec. Have you seen any clients
break?
The RFB spec states pretty clearly that a single
FramebufferUpdateRequest may generate 0 or more FramebufferUpdate
events. Once a client has sent a single FramebufferUpdate request, it
should expect to continue to receive more FramebufferUpdates for an
indefinite period of time according to the specification.
The reverse is true too - the server may coallese multiple
FramebufferUpdateRequest
into a single FramebufferUpdate reply. There is no 1-to-1 mapping between
request & reply as this patch attempts to enforce.
I have just re-read the rfb protocol spec and it specifies quite clearly
that framebuffer updates are sent in response to framebuffer update
requests.
However it is true that the server can collapse multiple requests in a
single reply. It is also clear that the reply can come at any time.
I have seen the linux vncviewer client breaking because of race
conditions due to this problem.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home