From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Fezc6-0005b7-DC
	for qemu-devel@nongnu.org; Sat, 13 May 2006 15:17:18 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Fezc3-0005ak-Ts
	for qemu-devel@nongnu.org; Sat, 13 May 2006 15:17:18 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Fezc3-0005ah-PE
	for qemu-devel@nongnu.org; Sat, 13 May 2006 15:17:15 -0400
Received: from [81.29.64.88] (helo=mail.shareable.org)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1Feze4-000248-TT
	for qemu-devel@nongnu.org; Sat, 13 May 2006 15:19:21 -0400
Received: from mail.shareable.org (localhost [127.0.0.1])
	by mail.shareable.org (8.12.8/8.12.8) with ESMTP id k4DJHBuY005660
	for <qemu-devel@nongnu.org>; Sat, 13 May 2006 20:17:11 +0100
Received: (from jamie@localhost)
	by mail.shareable.org (8.12.8/8.12.8/Submit) id k4DJHBqT005655
	for qemu-devel@nongnu.org; Sat, 13 May 2006 20:17:11 +0100
Date: Sat, 13 May 2006 20:17:11 +0100
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] Re: QEMU 0.8.1 and vnc
Message-ID: <20060513191710.GA32441@mail.shareable.org>
References: <28837826.1147436676713.JavaMail.root@eastrmwml07.mgt.cox.net>
	<446544E3.50208@codemonkey.ws>
	<Pine.LNX.4.64.0605131508330.11617@localhost>
	<200605131621.02743.paul@codesourcery.com>
	<44660E62.6050701@codemonkey.ws>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <44660E62.6050701@codemonkey.ws>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Anthony Liguori wrote:
> Exactly.  If you have a good network connection, you'll tend to get 
> lucky.  The conditions for this race to happen are 1) a server receives 
> a SetPixelFormat with a different BPP 2) the server has already sent 
> data on the wire in the previous BPP but the client did not receive it 
> before sending the SetPixelFormat message.
> 
> Changing the BPP is rare.  RealVNC does it because it attempts to be 
> smart about reducing bandwidth (it drops down to 8bpp and then goes back 
> up to 32bpp if the transfer rate is fast enough).
> 
> The best way to avoid this behavior is to use AutoSelect=0 FullColor=1 
> on the vncviewer command line.

How do other VNC servers avoid this problem, or do they all have it?

-- Jamie