Re: [Spice-devel] [protocol RFC 2/2] protocol: add SPICE_DISPLAY_CAP_HEAD

2012-05-07 Thread Alon Levy
On Mon, May 07, 2012 at 01:43:58PM +0200, Marc-André Lureau wrote: > On Mon, May 7, 2012 at 8:29 AM, Alon Levy wrote: > > Signifies that the client will support any SpiceDisplayMsgHead sent. > > What happens if the server has the capability but not the client? > > Should the client show the whol

Re: [Spice-devel] [protocol RFC 2/2] protocol: add SPICE_DISPLAY_CAP_HEAD

2012-05-07 Thread Marc-André Lureau
On Mon, May 7, 2012 at 8:29 AM, Alon Levy wrote: > Signifies that the client will support any SpiceDisplayMsgHead sent. What happens if the server has the capability but not the client? Should the client show the whole primary surface with its multiple heads, or quit with an error? Can the serve

[Spice-devel] [protocol RFC 2/2] protocol: add SPICE_DISPLAY_CAP_HEAD

2012-05-06 Thread Alon Levy
Signifies that the client will support any SpiceDisplayMsgHead sent. --- spice/protocol.h |4 1 file changed, 4 insertions(+) diff --git a/spice/protocol.h b/spice/protocol.h index e3342cb..b7d2bca 100644 --- a/spice/protocol.h +++ b/spice/protocol.h @@ -122,6 +122,10 @@ enum { SPIC