mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2024-12-24 13:42:16 +00:00
haproxy public development tree
4201ab791d
The mux ->detach() function currently takes a conn_stream. This causes an awkward situation where the caller cs_detach_endp() has to partially mark it as released but not completely so that ->detach() finds its endpoint and context, and it cannot be done later since it's possible that ->detach() deletes the endpoint. As such the endpoint link between the conn_stream and the mux's stream is in a transient situation while we'd like it to be clean so that the mux's ->detach() code can call any regular function it wants that knows the regular semantics of the relation between the CS and the endpoint. A better approach consists in slightly modifying the detach() API to better match the reality, which is that the endpoint is detached but still alive and that it's the only part the function is interested in. As such, this patch modifies the function to take an endpoint there, and by analogy (or simplicity) does the same for ->attach(), even though it looks less important there since we're always attaching an endpoint to a conn_stream anyway. It is possible that in the future the API could evolve to use more endpoints that provide a bit more flexibility in the API, but at this point we don't need to go further. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| BRANCHES | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README | ||
| ROADMAP | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
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)