From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:38973)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1S73Wh-0003Zx-AX
	for qemu-devel@nongnu.org; Mon, 12 Mar 2012 07:35:01 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1S73Wb-0007Ih-58
	for qemu-devel@nongnu.org; Mon, 12 Mar 2012 07:34:54 -0400
Received: from mx1.redhat.com ([209.132.183.28]:31968)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1S73Wa-0007IR-T7
	for qemu-devel@nongnu.org; Mon, 12 Mar 2012 07:34:49 -0400
Message-ID: <4F5DDF52.6040503@redhat.com>
Date: Mon, 12 Mar 2012 12:34:42 +0100
From: Gerd Hoffmann <kraxel@redhat.com>
MIME-Version: 1.0
References: <4F5CA590.1000605@redhat.com> <4F5CB429.4000907@codemonkey.ws>
	<20120311152528.GD7273@garlic.redhat.com>
	<4F5CC692.7050002@codemonkey.ws> <4F5DAC69.6010002@redhat.com>
	<4F5DB906.2030508@redhat.com> <4F5DC604.9010702@redhat.com>
	<20120312100307.GD6256@garlic> <4F5DCF6A.60008@redhat.com>
	<20120312112910.GG6256@garlic>
In-Reply-To: <20120312112910.GG6256@garlic>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [Spice-devel]  seamless migration with spice
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Hans de Goede <hdegoede@redhat.com>, "spice-devel@freedesktop.org" <spice-devel@freedesktop.org>, qemu-devel <qemu-devel@nongnu.org>, Anthony Liguori <anthony@codemonkey.ws>

On 03/12/12 12:29, Alon Levy wrote:
> On Mon, Mar 12, 2012 at 11:26:50AM +0100, Gerd Hoffmann wrote:
>>   Hi,
>>
>>> Migrate this struct n times for me.
>>
>> I think for the agent case this isn't needed.  Or is every client
>> allowed to speak to the agent in case of multiple clients connected?  I
>> somehow doubt this can work as the agent protocol can't multicast ...
>>
> 
> Actually the agent protocol does extend nicely to multiple clients - I
> forgot the name but there is an additional wrapper between the
> client/server originating message and the guest received message, that
> is currently used for server or client originating messages, and can be
> reused to have multiple in flight different client messages.

I think you'll have issues in the layer above though.  Two spice clients
doing cut+paste operations at the same time?  Two spice clients
requesting different screen resolutions?

cheers,
  Gerd