Re: mod_proxy in HTTPd

Chuck Murcko wrote:

> Totally agree. That's why we as mod_proxy commit to cutting a release of
> the web server too. Then users have what they want, in one package. Or a
> generic "apache rollup" build with the non-core modules put in.
> Mod_rewrite too?

(Puts on webmaster hat).

One important thing - there must also be no confusion as to which Apache release is the official released version.

If there are apache-x.x.x.tar.bz2, apache-proxy-x.x.x.tar.bz2, apache-TLS-x.x.x.tar.bz2, apache-proxy-TLS-x.x.x.tar.bz2 then users will be thoroughly confused.

There should be just one single apache-x.x.x.tar.bz released, with stable versions of everything included. At worst - a module should default to disabled, but these modules should definitely be there.

Regards,
Graham

-- 
-----------------------------------------
minfrin@sharp.fm		"There's a moon
					over Bourbon Street
						tonight..."

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related httpd.apache.org Links announce bugs cvs dev docs gui-dev modproxy-dev packagers testers Request more information about Pantek