The connection machinery behind HttpServer: a set of non-blocking connections, each with explicit
state that survives between pumps, serviced round-robin within per-pump budgets. Internal; kept out of
HttpServer so its members cannot collide with those of subclasses such as Application.
Connections are kept in service order. Each pump visits them from the front; afterwards the order becomes:
connections the pump did not reach, then connections that were refused a budgeted operation (a dispatch,
or I/O once the byte budget ran out), then everyone else. New connections join at the back. So a connection
that loses out in one pump is first in the next, however many new clients keep arriving.
The connection machinery behind
HttpServer: a set of non-blocking connections, each with explicit state that survives between pumps, serviced round-robin within per-pump budgets. Internal; kept out ofHttpServerso its members cannot collide with those of subclasses such asApplication.Connections are kept in service order. Each pump visits them from the front; afterwards the order becomes: connections the pump did not reach, then connections that were refused a budgeted operation (a dispatch, or I/O once the byte budget ran out), then everyone else. New connections join at the back. So a connection that loses out in one pump is first in the next, however many new clients keep arriving.