>>>>> "GS" == Greg Stark <[EMAIL PROTECTED]> writes: GS> 3) mod_proxy is poorly designed and poorly implemented. The main GS> deficiency is that each process is responsible for opening and GS> maintaining its connection to the backend. This defeats GS> keep-alives completely and forces a lot of overhead in the GS> kernel and the servers. You don't want keepalives on for the back-end anyhow. Connections over the local loop should be fast enough.
- Re: [RFC] modproxy:modperl rati... Vivek Khera
- Re: [RFC] modproxy:modperl rati... Dave Hodgkinson
- Re: [RFC] modproxy:modperl rati... Vivek Khera
- Re: [RFC] modproxy:modperl rati... Dave Hodgkinson
- Re: [RFC] modproxy:modperl rati... Perrin Harkins
- Re: modproxy:modperl ratios... Greg Stark
- Re: modproxy:modperl ratios... shane
- PerlSendHeader Benjamin Reed
- Re: PerlSendHeader Frank D. Cringle
- Re: modproxy:modperl ratios... Jeffrey W. Baker
- Re[2]: [RFC] modproxy:modperl r... Vivek Khera
- Re[2]: [RFC] modproxy:modperl r... Ilya Obshadko
- Re: [RFC] modproxy:modperl rati... Vivek Khera
- Re: Modperl/Apache deficiencies... Memory usage. shane
- Re: Modperl/Apache deficiencies... Memory usage. Doug MacEachern
- Re: Modperl/Apache deficiencies... Memory us... shane
- Re: Modperl/Apache deficiencies... Memor... Doug MacEachern
- Re: Modperl/Apache deficiencies... ... shane
- Re: Modperl/Apache deficiencies... Doug MacEachern
- RE: Modperl/Apache deficiencies... Memory usage. Paul G. Weiss
- RE: Modperl/Apache deficiencies... Memory usage. Matt Sergeant