On 09/08/2021 07:42 PM, Willy Tarreau wrote:
No rush on this one, I'll let you think about it, just let me know if we need to temporarily disable it from the CI, or if you just want a day or two of checking before knowing if you can get a quick solution or if it will take more time.
Thank you for understanding. For a start it would be good to exclude ot filter from the compilation process so as not to interfere with the development and testing of other code. Next, I could throw out the part related to context transfer via variables with #ifdef/#endif blocks, so that the ot filter code is compiled without it. After that the problem with variables could be solved without interfering with the rest of the coding/compilation process and the ot filter will be functional (except for the part with context transfer via variables, but the question is whether anyone uses it). The variable 'sess.ot.uuid' is just set, it is not used anywhere (as far as memory serves me). I imagined that this could be used if the user needs it, but it is not necessary. -- Zaga <miros...@zagorac.name> What can change the nature of a man?