> > I assume you plan to track MirCookie -> down-move-up gestures in mirserver -
> > so stating the MirCookie is sufficient to identify the specific touch
> contact
> > on the touchscreen or the specific pointing device, that when successfully
> > matched will be tracked for motion?
>
> Agreed, the window management policy needs the event to correctly interpret
> the request.
>
> I didn't fancy introducing a transport mechanism to forward input events from
> the client to the server. Tracking the latest event (like the existing
> tracking of its timestamp) on the server seems far simpler.
> > I assume you plan to track MirCookie -> down-move-up gestures in mirserver -
> > so stating the MirCookie is sufficient to identify the specific touch
> contact
> > on the touchscreen or the specific pointing device, that when successfully
> > matched will be tracked for motion?
>
> Agreed, the window management policy needs the event to correctly interpret
> the request.
>
> I didn't fancy introducing a transport mechanism to forward input events from
> the client to the server. Tracking the latest event (like the existing
> tracking of its timestamp) on the server seems far simpler.
yes...