On Wed, 23 Nov 2016, Christophe Fergeau wrote: > From: Francois Gouget <fgouget@xxxxxxxxxxxxxxx> > > The error is sent using the existing client stream report message where > the dropped frame count is maxed out while the received frame count is > zero. Servers that recognize it can then switch to sending regular > screen updates for that area so the client is not stuck with a frozen > area on the screen. > > This can be useful in case the client is unable to decode the stream for > some reason like a bug in the GStreamer plugins, the decoder not liking > odd video dimensions, etc. > > This can also happen when the client receives a message that the > server sent before it received the client's stream_report 'closing' a > stream. > > Also the client has to validate (and was validating) the server data > anyway so this is just about reporting errors rather than silently > ignoring them. > > Signed-off-by: Francois Gouget <fgouget@xxxxxxxxxxxxxxx> > Acked-by: Christophe Fergeau <cfergeau@xxxxxxxxxx> > --- Works or me. Same for the other patches in the series. -- Francois Gouget <fgouget@xxxxxxxxxxxxxxx> _______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/spice-devel