WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [PATCH] qemu vnc updates

To: Anthony Liguori <anthony@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH] qemu vnc updates
From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Date: Tue, 26 Feb 2008 16:22:24 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Delivery-date: Tue, 26 Feb 2008 08:23:05 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <47C43B37.1010209@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <47C3F6FA.6080506@xxxxxxxxxxxxx> <47C43B37.1010209@xxxxxxxxxxxxx>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
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.

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>