httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: AW: svn commit: r384580 - in /httpd/httpd/trunk/modules/proxy: mod_proxy.c mod_proxy.h mod_proxy_ajp.c proxy_util.c
Date Thu, 09 Mar 2006 23:21:14 GMT
=?iso-8859-1?Q?Pl=FCm=2C_R=FCdiger=2C_VIS?= wrote:
> 
> > von Garrett Rooney
> 
> >=20
> > Sticking per-backend info like ajp_flush_wait into the worker=20
> > object and the code to configure it in mod_proxy.c itself=20
> > seems very wrong to me.  There should be a per-backend=20
> > contect pointer to hold per-backend information, and the work=20
> > of handling worker parameters really should be pushed to a=20
> > per-backend callback or something like that.
> 
> I agree in general, but I guess in this case things are different.
> Although Jim chose names with ajp_ contained I think we can also
> use this to teach mod_proxy_http flushing. Not quite sure when I have
> time for this, but I want to give this a serious check as people also
> complainted frequently of this problem for mod_proxy_http.
> 
> 

Agreed. I'm +1 for making it non-AJP specific to handle
the other issues. But I wanted it to crawl before walk :)

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

Mime
View raw message