From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LLSnh-0000X1-3e for qemu-devel@nongnu.org; Fri, 09 Jan 2009 20:38:09 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LLSnf-0000Tt-JR for qemu-devel@nongnu.org; Fri, 09 Jan 2009 20:38:08 -0500 Received: from [199.232.76.173] (port=51583 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LLSnf-0000TY-8S for qemu-devel@nongnu.org; Fri, 09 Jan 2009 20:38:07 -0500 Received: from yw-out-1718.google.com ([74.125.46.153]:52985) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LLSne-0007GI-1r for qemu-devel@nongnu.org; Fri, 09 Jan 2009 20:38:06 -0500 Received: by yw-out-1718.google.com with SMTP id 6so3625786ywa.82 for ; Fri, 09 Jan 2009 17:38:05 -0800 (PST) Message-ID: <4967FC4C.3080201@codemonkey.ws> Date: Fri, 09 Jan 2009 19:39:24 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Ongoing changes to the displaying code References: <4966ADD4.5090102@codesourcery.com> <4966BB7A.3090303@codemonkey.ws> <4966BEC4.7080903@codemonkey.ws> <60cad3f0901090128m23977527kf658c15ba90dbaf8@mail.gmail.com> <49676B43.2020406@codemonkey.ws> <18791.34404.878201.724561@mariner.uk.xensource.com> <4967885A.2020908@codemonkey.ws> <20090109174252.GA2193@kos.to> <49679E7F.6050504@codemonkey.ws> <20090110000101.GB1972@shareable.org> In-Reply-To: <20090110000101.GB1972@shareable.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Jamie Lokier wrote: > The other concern with VNC might be its complexity means you really > always want to use the existing VNC client library, which may not be a > desirable dependency for some applications. For this, localhost-VNC > being both an extension to VNC and a subset of it would be helpful, as > you wouldn't have to use a full-fledged VNC client library for local > GUI apps if that isn't wanted. > As a protocol, VNC features are almost exclusively client driven. You can write an extremely simple client with very little code if you just avoid using advanced features. If all you care about is localhost using shared memory, this is entirely reasonable. Admittedly, there's a learning curve simply because there is a lot in VNC but the vast majority of it is optional. Regards, Anthony Liguori > -- Jamie > > >