People interested in mod_proxy have talked about that kind of scope several 
times.

It seems the constipation comes when we talk about current functionality.

I don't see a conflict in moving from the current code base to a new redesigned 
one. I just see the current code as a reference proxy for 2.0, and no more. 2.1 
or earlier would hopefully release with a redesigned, high performance proxy. 
But would  that design be a drop in replacement for the old one? Or would it 
give the new design more freedom to have mod_proxy_orig around to deal with 
that issue?

On Tuesday, February 6, 2001, at 07:13 PM, Sander van Zoest wrote:

> On Tue, 6 Feb 2001, Philippe M . Chiasson wrote: 
>  
> > I know of at least 2 very different uses for the mod_proxy module 
> > currently. 
> > The first one is to act as a caching HTTP proxy, but the second is to make 
> > a 
> > lightweight doc server proxy some requests to a heavyweight server 
> > (mod_perl). 
> > There 2 jobs share some common code/functionnality but there are also quite 
> > different. 
> >  
> > I think it would be wise to consider splitting these 2 tasks up to. 
>    
> Although it should considered, I think the power of an apache proxy server 
> would be the fact that it could do both of these tasks. I would consider 
> a proxy type of project to be more along the lines of what Dean Gaudet has 
> been refering to as an "http router". Everyone is doing this one way or  
> another and this is also part of squid now (with their accelerated support). 
>  
> If some people add a reliable cache that talks HTCP and ICP and whatever they 
> feel is useful that would be a bonus. Having access via different languages 
> to 
> the proxy/router stream can be very beneficial as well. 
>  
> Maybe if the project would come out with that sort of scope more people would 
> be interested in helping out. I would definately use it and submit patches 
> if I can not find the time to work on it in a fuller capacity. 
>  
> -- 
> Sander van Zoest                                         [EMAIL PROTECTED] 
> Covalent Technologies, Inc.                           
> http://www.covalent.net/ 
> (415) 536-5218                                 
> http://www.vanzoest.com/sander/ 
>  
>  
>  
>  

Chuck Murcko
Topsail Group
http://www.topsail.org/

Reply via email to