From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:41302) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S74W2-0005QU-I2 for qemu-devel@nongnu.org; Mon, 12 Mar 2012 08:38:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S74Vw-00048q-5w for qemu-devel@nongnu.org; Mon, 12 Mar 2012 08:38:18 -0400 Received: from mx1.redhat.com ([209.132.183.28]:25529) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S74Vv-00048c-P5 for qemu-devel@nongnu.org; Mon, 12 Mar 2012 08:38:12 -0400 Date: Mon, 12 Mar 2012 13:45:48 +0200 From: Alon Levy Message-ID: <20120312114548.GI6256@garlic> References: <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> <4F5DDF52.6040503@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F5DDF52.6040503@redhat.com> Subject: Re: [Qemu-devel] [Spice-devel] seamless migration with spice List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: Anthony Liguori , Hans de Goede , qemu-devel , "spice-devel@freedesktop.org" On Mon, Mar 12, 2012 at 12:34:42PM +0100, Gerd Hoffmann wrote: > 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? Yeah, you're right of course, this needs to be dealt with somehow. cut+paste: maps nicely to a number of different buffers. Would need some policy, and the session agent becomes closer to a buffer manager. resolutions: again policy, perhaps have a master client, or if none defined let the last or just the first choose. Not sure. But these issues don't need to be solved now, do they? > > cheers, > Gerd > > _______________________________________________ > Spice-devel mailing list > Spice-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/spice-devel