Lines Matching full:requests

10 client requests.  The original design was simplistic; under the maximum
66 With a single client executing a stream of requests:
68 	A client sends a packet of requests to the server.
74 	full of requests from the client
76 	The server executes requests from this buffer until it emptys,
77 	in two stages -- 10 requests at a time are executed in the
78 	inner Dispatch loop, a buffer full of requests are executed
80 	have complete requests pending in their input queues.
84 	WaitForSomething; now that the client has no requests pending,
89 With multiple clients sending streams of requests, the sequence
91 set isItTimeToYield after each 10 requests executed causing the
92 server to round-robin among the clients with available requests.
94 It's important to realize here that any complete requests which have been
102 The X server executes at most a buffer full of requests before again heading
119 	when those clients are executing slow requests.
121  3	The server calls select too often when executing fast requests.
136 and execute requests for the entire timeslice before yielding to
140 complete requests queued, the server should go through select each
148 is busy, another buffer full of requests will already be waiting
152 Finally, the dispatch loop should not simply execute requests from the
177 executing requests from all available clients, a single client
178 is chosen after each call to WaitForSomething, requests are
189  2.	Clients which have executed no requests for some time