Lines Matching full:clients

79 	because WaitForSomething immediately returns if any clients
89 With multiple clients sending streams of requests, the sequence
92 server to round-robin among the clients with available requests.
95 read from clients will be executed before the server will use select again
96 to discover input from other clients.  A single busy client can easily
99 So, the X server doesn't share well with clients which are more interactive
107 the server also runs busy clients less efficiently than is would be
118  	aggressive clients in the face of busy clients, especially
119 	when those clients are executing slow requests.
123  4	Some priority scheme is needed to keep interactive clients
139 Instead of returning immediately from WaitForSomething if clients have
141 time and gather as many ready clients as possible.  This involves
154 busy clients penalized and clients receiving user events praised.
177 executing requests from all available clients, a single client
185  1.	Clients which consume their entire slice are penalized
189  2.	Clients which have executed no requests for some time
193  3.	Clients which receive user input are praised by having