b73262fc85
This makes SE_FL_APPLET_NEED_CONN autonomous, in that we check for it everywhere we have a relevant cs_rx_blocked(), so that the flag doesn't need anymore to be covered by cs_rx_blocked(). Indeed, this flag doesn't really translate a receive blocking condition but rather a refusal to wake up an applet that is waiting for a connection to finish to setup. This also ensures we will not risk to set it back on a new endpoint after cs_reset_endp() via SE_FL_APP_MASK, because the flag being specific to the endpoint only and not to the connector, we don't want to preserve it when replacing the endpoint. It's possible that cs_chk_rcv() could later be further simplified if we can demonstrate that the two tests in it can be merged.
The HAProxy documentation has been split into a number of different files for ease of use. Please refer to the following files depending on what you're looking for : - INSTALL for instructions on how to build and install HAProxy - BRANCHES to understand the project's life cycle and what version to use - LICENSE for the project's license - CONTRIBUTING for the process to follow to submit contributions The more detailed documentation is located into the doc/ directory : - doc/intro.txt for a quick introduction on HAProxy - doc/configuration.txt for the configuration's reference manual - doc/lua.txt for the Lua's reference manual - doc/SPOE.txt for how to use the SPOE engine - doc/network-namespaces.txt for how to use network namespaces under Linux - doc/management.txt for the management guide - doc/regression-testing.txt for how to use the regression testing suite - doc/peers.txt for the peers protocol reference - doc/coding-style.txt for how to adopt HAProxy's coding style - doc/internals for developer-specific documentation (not all up to date)