You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@httpd.apache.org by Jim Jagielski <ji...@jaguNET.com> on 2006/04/01 16:55:50 UTC

Re: svn commit: r390599 - /httpd/httpd/branches/2.2.x/STATUS

pquerna@apache.org wrote:
> 
> Author: pquerna
> Date: Fri Mar 31 22:33:47 2006
> New Revision: 390599
> 
> URL: http://svn.apache.org/viewcvs?rev=390599&view=rev
> Log:
> I am not comfortable with this solution for making the flushing band aid configurable. I do not oppose the concept, just the placement of the configuration information inside of the mod_proxy core, and not in mod_proxy_ajp.
> 

The main reason why it's in mod_proxy (and the various elements
renamed from ajp_foo to foo) is that as we extend mod_proxy
for other protocols, same packet-based like AJP, this will
likely be a common problem. Even in non-packet based
protocols, I can see wanting some level of admin control.

-- 
===========================================================================
   Jim Jagielski   [|]   jim@jaguNET.com   [|]   http://www.jaguNET.com/
	    "If you can dodge a wrench, you can dodge a ball."