15252cd9c0
The following flags are not at all related to the endpoint but to the connector itself: - SE_FL_RXBLK_ROOM - SE_FL_RXBLK_BUFF - SE_FL_RXBLK_CHAN As such they have no business staying in the endpoint descriptor and they must move to the stream connector. They've also been renamed accordingly to better match what they correspond to (the same name as the function that sets them). The rare occurrences of cs_rx_blocked() were replaced by an explicit test on the list of flags. The reason is that cs_rx_blocked() used to preserve some tests that are not needed at certain places since already known. For the same reason SE_FL_RXBLK_ANY wasn't converted. As such it will later be possible to carefully review these few locations and eliminate the unneeded flags from the tests. No particular function was made to test them since they're explicit enough. It now looks like ci_putchk() and friends could very well place the flag themselves on the connector when they detect a buffer full condition, as this would significantly simplify the high-level API. But all usages must first be reviewed before this simplification can be done. For now it remains done by applet_put*() instead.
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)