> After checking Apache code for mod_proxy looks like it is normal
behaviour.
> File modules/proxy/proxy_util.c function ap_proxy_send_fb. This function
> reads from originating server into buffer and then writes to the customer
from
> this buffer. BUT the socket is closed AFTER all the data is sent to the
> client (file module/proxy/proxy_http.c function ap_proxy_http_handler. So
> the heavy mod_perl server is not released for serving other requests
untill
> the data is sent to the client by proxy.
>
> Maybe I'm missing something but the practice shows that this is true and
Guide
> contains error.
Maybe the thing you're missing is that mod_proxy takes care of the lingering
close. Those of us who have tried the two-server setup have all seen
dramatic reductions in the number of mod_perl processes required.
- Perrin
