On Oct 22, 2008, at 3:01 PM, Ruediger Pluem wrote:
Agreed that the mod_proxy_http.c patch looks reasonable at 1st
blush, but need to look into all possible interaction with the
change to a shorter-lived pool.
There is an explanation above the code why we should take connection-
>pool,
but IMHO it is outdated and goes back to the times where there was a
direct
connection between the backend connection and the frontend connection.
With the usage of the connection pools this is no longer the case
and I
cannot think of any reason why not using r->pool instead.
Yeppers... digging in, and looking over the past history, the
move to the req pool is the right one. But that's the only aspect
which, imo, we need to patch right now.
Patching as we speak.
