tree a6a2c0dee0ba2fe3bac5279d154e270907add778
parent 3bf1b2b816e4e8e3154bd50b3b5a277cf3d363d8
author Willy Tarreau <wtarreau@exceliance.fr> 1346093614 +0200
committer Willy Tarreau <w@1wt.eu> 1346698053 +0200

MAJOR: channel: remove the BF_FULL flag

This is similar to the recent removal of BF_OUT_EMPTY. This flag was very
problematic because it relies on permanently changing information such as the
to_forward value, so it had to be updated upon every change to the buffers.
Previous patch already got rid of its users.

One part of the change is sensible : the flag was also part of BF_MASK_STATIC,
which is used by process_session() to rescan all analysers in case the flag's
status changes. At first glance, none of the analysers seems to change its
mind base on this flag when it is subject to change, so it seems fine not to
add variation checks here. Otherwise it's possible that checking the buffer's
input and output is more reliable than checking the flag's replacement.