d9c1d33fa1
It is now possible to start an appctx on a thread subset. Some controls were added here and there. It is forbidden to start a backend appctx on another thread than the local one. If a frontend appctx is started on another thread or a thread subset, the applet .init callback function must be defined. This callback function is responsible to finalize the appctx startup. It can be performed synchornously. In this case, the appctx is started on the local thread. It is not really useful but it is valid. Or it can be performed asynchronously. In this case, .init callback function is called when the appctx is woken up for the first time. When this happens, the appctx affinity is set to the current thread to be able to start the session and the 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)