From: "Daniel P. Berrange" <berrange@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: xen-devel@lists.xensource.com,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Re: [PATCH] qemu vnc updates
Date: Tue, 26 Feb 2008 16:22:24 +0000 [thread overview]
Message-ID: <20080226162224.GI30568@redhat.com> (raw)
In-Reply-To: <47C43B37.1010209@codemonkey.ws>
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 -=|
next prev parent reply other threads:[~2008-02-26 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 11:24 [PATCH] qemu vnc updates Stefano Stabellini
2008-02-26 16:15 ` Anthony Liguori
2008-02-26 16:22 ` Daniel P. Berrange [this message]
2008-02-26 16:34 ` Stefano Stabellini
2008-02-26 17:29 ` Anthony Liguori
2008-02-26 17:56 ` Stefano Stabellini
2008-02-26 19:20 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080226162224.GI30568@redhat.com \
--to=berrange@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.