mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-03-09 09:01:51 +01:00
Sending is implemented in two parts on quic-conn module. First, QUIC packets are prepared in a buffer and then sendto() is called with this buffer as input. qc.tx.buf is used as the input buffer. It must always be empty before starting to prepare new packets in it. Currently, this is guarantee by the fact that either sendto() is completed, a fatal error is encountered which prevent future send, or a transient error is encountered and we rely on retransmission to send the remaining data. This will change when poller subscribe of socket FD on sendto() transient error will be implemented. In this case, qc.tx.buf will not be emptied to resume sending when the transient error is cleared. To allow the current sending process to work as expected, a new function qc_purge_txbuf() is implemented. It will try to send remaining data before preparing new packets for sending. If successful, txbuf will be emptied and sending can continue. If not, sending will be interrupted. This should be backported up to 2.7.
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)
Description
Languages
C
98.1%
Shell
0.9%
Makefile
0.5%
Lua
0.2%
Python
0.1%