From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LYfH8-0002XO-U8 for qemu-devel@nongnu.org; Sun, 15 Feb 2009 06:35:07 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LYfH6-0002R1-Sj for qemu-devel@nongnu.org; Sun, 15 Feb 2009 06:35:05 -0500 Received: from [199.232.76.173] (port=55058 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LYfH4-0002QQ-A3 for qemu-devel@nongnu.org; Sun, 15 Feb 2009 06:35:02 -0500 Received: from mx1.redhat.com ([66.187.233.31]:45218) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LYfH3-0001qG-S7 for qemu-devel@nongnu.org; Sun, 15 Feb 2009 06:35:01 -0500 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n1FBZ1jN030676 for ; Sun, 15 Feb 2009 06:35:01 -0500 Received: from file.fab.redhat.com (file.fab.redhat.com [10.33.63.6]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n1FBZ0An023367 for ; Sun, 15 Feb 2009 06:35:01 -0500 Received: from file.fab.redhat.com (localhost.localdomain [127.0.0.1]) by file.fab.redhat.com (8.13.1/8.13.1) with ESMTP id n1FBZ04v004486 for ; Sun, 15 Feb 2009 11:35:00 GMT Received: (from berrange@localhost) by file.fab.redhat.com (8.13.1/8.13.1/Submit) id n1FBZ0ZK004482 for qemu-devel@nongnu.org; Sun, 15 Feb 2009 11:35:00 GMT Date: Sun, 15 Feb 2009 11:35:00 +0000 From: "Daniel P. Berrange" Subject: Re: [Qemu-devel] [PATCH] Support multiple VNC clients Message-ID: <20090215113500.GD4795@redhat.com> References: <4995CECB.1070401@moose.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4995CECB.1070401@moose.net> Reply-To: "Daniel P. Berrange" , 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 On Fri, Feb 13, 2009 at 02:49:31PM -0500, Brian Kress wrote: > Attached is a patch that allows qemu to support multiple vnc clients. > Each client can have their own > VNC encodings and VNC state. > > General idea: > > Change structure associated with a display from VncState to a new > structure VncDisplay. > Remove client specific fields from VncDisplay. > Remove display specific fields from VncState. > Maintain a linked list of VncStates per VncDisplay structure, update as > necessary. > When updates/resizes/copies come in from the hardware, dispatch to all > clients. > > > Patch is against current SVN (6618) > Any ideas/suggestions/comments/flames appreciated. Perhaps also add a -vnc command line flag to let us control policy for multiple clients interactions ? eg some policies I think of - Single client, new clients dropped - Single client, original client dropped - Many clients, first full access, others view only - Many clients, all full access Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|