httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip A. Prindeville" <phil...@enteka.com>
Subject Re: [PATCH] for 1.2.X: proxy screwup
Date Fri, 15 Aug 1997 01:07:35 GMT
> Date: Wed, 13 Aug 1997 23:18:10 +0100 (BST)
> From: Paul Sutton <paul@ukweb.com>
> To: new-httpd@apache.org
> Subject: Re: [PATCH] for 1.2.X: proxy screwup

> On Wed, 13 Aug 1997, Lars Eilebrecht wrote:
> > According to Randy Terbush:
> > > > Do we want to hold 1.2.3 for this?  I would say yes.
> > > 
> > > I would vote +1 to hold. It would be nice if this could be our last 
> > > 1.2 release.
> > 
> > mod_proxy has some other flaws...  see PRs 656, 763, 812, 870 and 974.
> > Most of them should be easy to fix (I had the intention to fix
> > some of the bugs myself, but haven't found the time yet.)

> Is there perhaps an argument for unbundling mod_proxy from the rest of
> Apache? It is a significant module that can stand on its own feet and
> really provides a completely different (and complementary) set of
> funtionality to that provided by the rest of Apache.

> I guess I am thinking about unbundling it because it seems to be developed
> on a different release cycle to the rest of Apache. While we are actively
> chasing bugs and moving to a feature freeze on the rest of Apache,
> mod_proxy is in some ways rather left behind, with outstanding bugs and
> (if the 1.2 feature freeze is any example) not entering a feature freeze
> at all. 

Well, it would be a good test of module-to-core interface's robustness,
and how well a module "drops in" after two independent source trees have
been modified separately.

> I'm not suggesting that the proxy module is not a valuable and well
> developed application, just that perhaps Apache-the-proxy server should be
> more of distinct project from Apache-the-web-server. 

> //pcs

-Philip

Mime
View raw message