tree 3fd336128e87083ff1a8f900d773e6f7d3e2edc5
parent babd05a6c6d3a9f835b0f978c7f159d06338eb58
author Willy Tarreau <wtarreau@exceliance.fr> 1345197304 +0200
committer Willy Tarreau <w@1wt.eu> 1346615591 +0200
encoding latin1

MEDIUM: connection: add definitions for dual polling mechanisms

The conflicts we're facing with polling is that handshake handlers have
precedence over data handlers and may change the polling requirements
regardless of what is expected by the data layer. This causes issues
such as missed events.

The real need is to have three polling levels :
  - the "current" one, which is effective at any moment
  - the data one, which reflects what the data layer asks for
  - the sock one, which reflects what the socket layer asks for

Depending on whether a handshake is in progress or not, either one of the
last two will replace the current one, and the change will be propagated
to the lower layers.

At the moment, the shutdown status is not considered, and only handshakes
are used to decide which layer to chose. This will probably change.