On Thu, 11 Oct 2012 13:00:40 +0200
David Herrmann wrote:
> Hi Pekka
>
> On Wed, Oct 10, 2012 at 11:47 AM, Pekka Paalanen wrote:
> > This change breaks the protocol.
> >
> > The current protocol is racy in that updates to surface content and
> > surface state (e.g. damage, input and opaque regio
Hi Pekka
On Wed, Oct 10, 2012 at 11:47 AM, Pekka Paalanen wrote:
> This change breaks the protocol.
>
> The current protocol is racy in that updates to surface content and
> surface state (e.g. damage, input and opaque regions) are not guaranteed
> to happen at the same time. Due to protocol buff
This change breaks the protocol.
The current protocol is racy in that updates to surface content and
surface state (e.g. damage, input and opaque regions) are not guaranteed
to happen at the same time. Due to protocol buffering and handling
practices, the issues are very hard to trigger.
Committi
