httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Reid" <ab...@dial.pipex.com>
Subject Re: axe proxy support from 2.0?
Date Fri, 12 Nov 1999 19:09:06 GMT
Rather than discussing NOT removing something, should we talk about what we
WANT in the new "proxy/file getter/cache/whatever we want to call it"?

Might be more productive and then sets the targets for someone to start...

Just my 2p...

david
----- Original Message -----
From: <tvaughan@aventail.com>
To: <new-httpd@apache.org>
Sent: 12 November 1999 18:17
Subject: Re: axe proxy support from 2.0?


> Graham Leggett <minfrin@sharp.fm> writes:
>
> > Greg Stein wrote:
> >
> > > All right. Axe the proxy thing. Build in specific support for grabbing
> > > files from elsewhere. If that goes best into the layering, as another
APR
> > > type, or whatever, then it is clear what is going on.
> > >
> > > It seems that we could simplify a lot of our life if we stopped
viewing it
> > > as a (reverse) proxy and viewed/built it as a set of
> > > functions/types/whatever for fetching remote files. Certainly a lot
easier
> > > to build (rather than porting/rebuilding mod_proxy for 2.0).
> >
> > This is true - though this encompasses about 90% of the existing proxy
> > code anyway. Remember that the ftp and http "client" bits as well as the
> > caching engine all have significant use inside the reverse proxy,
> > especially the caching - it makes a huge difference on a busy server.
> > Even the parent cache support is useful to connect the reverse proxy
> > through a further proxy.
>
> The cache is key. We've seen latency times increase by as much as a factor
> of six without it. (The more cache friendly an origin server is, the
> better.) It might be useful to abstract the cache out as well. I suppose
> mod_include might want to cache a document it somehow knows can be cached.
>
> The ability to add other protocols, like ones that start with 'H' and end
> with 'S', would be nice too.
>
> -Tom
>
> --
> Tom Vaughan <tvaughan at aventail dot com>


Mime
View raw message