From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LYrqQ-0001h0-0K
	for qemu-devel@nongnu.org; Sun, 15 Feb 2009 20:00:22 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LYrqN-0001gh-Bx
	for qemu-devel@nongnu.org; Sun, 15 Feb 2009 20:00:21 -0500
Received: from [199.232.76.173] (port=49775 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LYrqN-0001ge-6n
	for qemu-devel@nongnu.org; Sun, 15 Feb 2009 20:00:19 -0500
Received: from yx-out-1718.google.com ([74.125.44.156]:61189)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1LYrqM-0007fy-SH
	for qemu-devel@nongnu.org; Sun, 15 Feb 2009 20:00:18 -0500
Received: by yx-out-1718.google.com with SMTP id 4so1271053yxp.82
	for <qemu-devel@nongnu.org>; Sun, 15 Feb 2009 17:00:17 -0800 (PST)
Message-ID: <4998BA84.3020104@codemonkey.ws>
Date: Sun, 15 Feb 2009 18:59:48 -0600
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH] Support multiple VNC clients
References: <4995CECB.1070401@moose.net>
	<20090215113500.GD4795@redhat.com>	<004e01c98fb7$68673070$39359150$@com>
	<4998957B.8000807@moose.net>
In-Reply-To: <4998957B.8000807@moose.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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

Brian Kress wrote:
> Itamar Heim wrote:
>>> From: qemu-devel-bounces+iheim=redhat.com@nongnu.org 
>>> [mailto:qemu-devel-
>>>     
>> ...
>>  
>>> 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
>>>     
>> [IH] also - how does one specify the password for a specific vnc via the
>> monitor?
>>   
>    The password (as well as all the other authentication parameters) 
> apply to the display, not
> a specific client.  Even with this patch you still only have one vnc 
> display, so you change the
> password for that display the same way you did before this patch.

I'm inclined to take this patch as-is.  We can follow up with additional 
features.

Regards,

Anthony Liguori

>
>    -Brian
>
>
>
>
>