Lines Matching full:requests

9 * A `Client` begins in the **idle** state with no socket connection and no requests in queue.
10 …* The *connect* event transitions the `Client` to the **pending** state where requests can be queu…
11 … transition the `Client` to the **destroyed** state. Since there are no requests in the queue, the…
12 …cates the underlying socket connection has been successfully established and requests are queueing.
13 …* The *process* event transitions the `Client` to the **processing** state where requests are proc…
14 …* If requests are queued, the *close* event transitions to the **processing** state; otherwise, it…
18 … After all queued requests are completed, the *keepalive* event transitions the `Client` back to t…
19 …t` still has queued requests, the `Client` transitions to the **process.closing** state where it w…
21 … `Client` from the **processing** state to the **destroyed** state, destroying any queued requests.
34 …troyed**](#destroyed) state since the `Client` instance will have no queued requests in this state.
38 …ring `Client` instantiation. The internal queue is initially empty, and requests can start queuein…
40 …osecallback) with queued requests, transitions the `Client` to the [**processing**](#processing) s…
42 …ack) transitions directly to the [**destroyed**](#destroyed) state regardless of existing requests.
46 …` is in this state. `Client.dispatch()` will add more requests to the queue while existing request…
50 …requests are being processed in a FIFO order. If a request body requires draining, the *needDrain*…
54 …eam.html) and requires draining. The `Client` cannot process additional requests while in this sta…
58 …requests and the [`Client.close()`](Client.md#clientclosecallback) method is called. In this state…