Path: utzoo!attcan!uunet!lll-winken!lll-lcc!mordor!joyce!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!ZERMATT.LCS.MIT.EDU!RWS
From: RWS@ZERMATT.LCS.MIT.EDU (Robert Scheifler)
Newsgroups: comp.windows.x
Subject: Re: xset m accl. theres. and XNextEvent (MotionNotify)
Message-ID: <19880630160207.4.RWS@KILLINGTON.LCS.MIT.EDU>
Date: 30 Jun 88 16:02:00 GMT
References: <2865@umd5.umd.edu>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 8

Most people believe mouse compression should be done in the server.
Doing this "right" probably requires kernel support (the X motion
history buffer should probably be maintained in the kernel), but we have
no control over device drivers.  The current server internals assume
that the ddx layer (somehow) compresses events, but most currently do
not (at least not as we shipped in R2).

XCompressEvents in X10 was only on the client side; the motion
hint stuff in the X11 protocol was designed as an improvement.