Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Sender: jesus
Message-ID: <3A8C289B.D99FF92D@omniti.com>
Date: Thu, 15 Feb 2001 14:05:41 -0500
From: "Theo E. Schlossnagle" <theo@omniti.com>
Organization: Center for Networking and Distributed Systems
MIME-Version: 1.0
To: new-httpd@apache.org
Subject: Re: [mod_proxy] Help offered
References: <20010206190306.E4793@hbesoftware.com>
 <Pine.BSF.4.21.0102061608060.75094-100000@escher.vanzoest.com>
 <20010206182524.Q26044@lyra.org> <001701c090b3$bbf909e0$6401a8c0@apache>
 <20010207010255.V26044@lyra.org> <3A8ADC57.C845A5BB@sharp.fm>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Since we are talking about mod_proxy, I will assume that you are referring to
the 1.3.x mod_proxy -- as it doesn't work with 2.0 (yet?).

What you say is deceiving.  Squid is much more effecient for high volume
proxying than Apache 1.3.x.  It's implementation supports several thousands of
concurrently open sessions.  Also, it is quite trvial to modify Squid to
handle "virtual hosting".  The point is that squid is transparent... It
doesn't care what is behind it.  With relatively small modifications, you can
put Squid in front of several URL variants and it will work with logging to
seperate files.  It is also trivial to hack Squid to support Apache style
commonlog formatting strings.

Most big sites that _really_ need something like this, just make these changes
to suit their needs.

Squid's purpose in life it to be transparent.  So, you do loose some features
like being able to use mod_rewrite to "glue" several backend machines together
into a unified namespace on the front.  Hacking mod_rewrite functionality into
Squid is a much harder problem IMHO.

It makes complete sense to me to partition mod_proxy from the httpd-2.0 tree. 
Once it is lean and mean and performs _only_ the things a core module should,
then stick it back in.  If people _need_ that functionality, then for now they
download it separately. 

I am starting to see mod_proxy hold up httpd-2.0 development -- that scares
me.

Graham Leggett wrote:
> Squid and NSPS are only useful in trivial reverse proxy situations,
> where you have one frontend website URL, and your entire webspace is
> proxied to one or more HTTP backends. Try and do anything more
> complicated and you're stuck.

-- 
Theo Schlossnagle
1024D/A8EBCF8F/13BD 8C08 6BE2 629A 527E  2DC2 72C2 AD05 A8EB CF8F
2047R/33131B65/71 F7 95 64 49 76 5D BA  3D 90 B9 9F BE 27 24 E7