On Mon, Mar 12, 2012 at 04:24:16PM +0200, Alon Levy wrote: > On Mon, Mar 12, 2012 at 01:44:47PM +0100, Gerd Hoffmann wrote: > > On 03/12/12 12:45, Alon Levy wrote: > > > On Mon, Mar 12, 2012 at 12:34:42PM +0100, Gerd Hoffmann wrote: > > >> On 03/12/12 12:29, Alon Levy wrote: > > >>> > > >>> 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? > > > > Surely not. But better keep it in mind when figuring how to handle > > migration, so we are prepared to xfer all needed state in case we > > implement that some day. > > > > How does multi-client handle this today? > > Just a single agent iirc. Or perhaps it breaks.. s/agent/client/, i.e. just one of the clients gets to have client mouse, c&p, resolution changes (well, all the rest get affected by the triggered resolution changes). IOW, left as a todo.
> > > > > cheers, > > Gerd > > _______________________________________________ > > Spice-devel mailing list > > spice-de...@lists.freedesktop.org > > http://lists.freedesktop.org/mailman/listinfo/spice-devel >
