Hi, > The scheme I had in mind was this: > > - When a new non-a8-capable client appears, don't send it any of the > a8 surfaces > > - If the client doesn't understand a8 surfaces, > > - keep all a8 surfaces rendered on the server side > > - if the guest sends a command using an a8 surface as a > destination, simply render the command on the server side > > - if the client sends a command using an a8 surface as a source, > rewrite the image object to be a real image referring to the > server side bits (which are also sent or possibly cached) > rather than a surface Hmm, when the server is able to translate a8 ops into non-a8 ops using server-side rendering, then there is no need to notify the guest about the client capabilities. > But it's much simpler to just say that the guest should stop referring > to a8 surfaces if the client can't handle them. Not sure about that, this move might just shift the complexity from spice-server to the guest qxl driver. cheers, Gerd _______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/spice-devel