>The only non-blocking functions available to use is via "socket class". Is
it too crazy if we use "socket object" to do network IO to a process we
write that acts as a proxy to do disk operations?
Feels stupid that I mentioned this, if we're going this far, just use SPOE
instead.
On Mon, Oct 17,
Hi Aurelien,
I really appreciate the response. This confirms, that "everything in
runtime mode" uses the same thread pool as HTTP workers. This also says
that the onlytime we can use "blocking IO" is in "initialization mode", ie,
at HAproxy startup/reloads.
I shared the ACL example, but this is w
Hello,
I am trying to clarify in which case a tcp connection might be closed
following those rules:
- http-request return
- http-request deny
unless I missed something I have not been able to see the answer within the doc.
General context being, we are using `option http-keep-alive`; also our
hap
Hi,
it feels like that shouldn't be true for "background tasks" as it is
mentioned that they run in separate threads
That's not 100% true. Lua tasks do run concurrently with the rest of
HAProxy processing.
But they don't run in separate "threads": they run in separate haproxy
tasks.
What this
Hi
On 10/16/22 20:49, Cyril Bonté wrote:
* I've also noticed that the quick reference on docker hub still
references https://cbonte.github.io/haproxy-dconv/. I'm not sure about
who maintains this page but it may be a good idea to update to haproxy.org.
See https://hub.docker.com/_/haproxy
I'v
5 matches
Mail list logo
