mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-25 07:41:36 +02:00
e645d88c6b
Depending on the context, we know the endpoint or the application attached to the conn_stream is defined and we know its type. However, having accessors testing the endpoint or the application may lead the compiler to report possible null derefs here and there. The alternative is to add useless tests or use ALREAD_CHECKED/DISGUISE macros. It is tedious and inelegant. So now, similarily to the ob API, the safe API, testing endpoint/application, relies on an unsafe one (same name prefixed with '__'). This way, any caller may use the unsafe API when it is relevant. In addition, there is no reason to test the conn-stream itself. It is the caller responsibility to be sure there is a conn-stream to get its endpoint or its application. And most of type, we are sure to have a conn-stream.
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)