| From: Raja Subramanian
| Hmmm... I would like to point out that it's the X server
| that reads the mouse device not the window manager.
| And following this logic, it will be the X server that
| gets all the CPU.
Yep, you are correct. The display server receives the user inputs
- mouse, keyboard etc. These signals are sent to the remote
(or local) client apps. This ideally makes both the server and
client as I/O bound processes becuase both, apart from other work,
wait for signals.
But can't say anything abt the server's priority if its running on
Windows :(
saha
--