Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!snorkelwacker!bloom-beacon!LARRY.MCRCIM.MCGILL.EDU!mouse
From: mouse@LARRY.MCRCIM.MCGILL.EDU (der Mouse)
Newsgroups: comp.windows.x
Subject: Re: window manager traffic
Message-ID: <9006040036.AA15884@Larry.McRCIM.McGill.EDU>
Date: 4 Jun 90 00:36:14 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 25

>> DEC may have done the right with their new X terminal by putting the
>> WM in the server.  [...]  It would probably be better to have
>> multiple loadable WM's, but I'm sure we could live with a single
>> hardcoded one.

For what it's worth, I couldn't.

> Much of the network traffic is due to historical reasons.  Older
> workstations such as the Vaxstation I and II were not fast enough to
> supply the WM with MotionNotify events sufficient to keep move/resize
> outlines tracking the mouse.  Because of this, some window managers
> will send off QueryPointer requests rather than letting the server
> supply MotionNotify events.  This makes performance look much better
> on slower workstations.

Isn't this what pointer motion hints are all about?  My window manager
used to depend on MotionNotify, but performance over a slow network was
very bad (the tracking would fall behind the mouse, though it would
catch up if you let the mouse sit still).  I changed it to use motion
hints and it works fine now.

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu