[PATCH RFC inputproto] specs: Don't allow for early acceptance/rejection

[Peter Hutterer]

Definition of early acceptance/rejection: If supported, a client may accept
or reject a touch sequence before it becomes the current owner of the
sequence. In some cases, this can speed up touch processing as it removes
one ore more clients from the listeners and thus reduce the number of events
to send and process client-side.

Unfortunately, we likely won't have time to implement early
acceptance/rejection for XI 2.2 so drop it from the protocol. This can
easily be added in XI 2.3 if we get the time to implement it.

Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>
---
I'm going to hold this patch back until we really can't get the patches
into the server anymore but I really doubt we'll get this feature in time.
It's quite easy to add to XI 2.3 (reverting this patch) once we have the
implementation in place.

Meanwhile, a heads up, this part will likely be dropped from 2.2

 specs/XI2proto.txt |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/specs/XI2proto.txt b/specs/XI2proto.txt
index 10f953a..e1b5b8a 100644
--- a/specs/XI2proto.txt
+++ b/specs/XI2proto.txt
@@ -1449,8 +1449,8 @@ later than the current X server time. The time parameter must be CurrentTime for
 requests with event modes of AcceptTouch and RejectTouch.
 
 When event-mode is AcceptTouch, a BadValue error occurs if the touch ID is
-invalid. A BadAccess error occurs if this client is not the current or potential
-owner of the specified touch ID.
+invalid. A BadAccess error occurs if this client is not the current owner of
+the specified touch ID.
 
 The following describes the processing that occurs depending on what constant
 you pass to the event-mode argument:
-- 
1.7.7.5