On Wed, Feb 07, 2001 at 04:25:37PM -0500, Chuck Murcko wrote: >... > > On Wed, Feb 07, 2001 at 01:23:18AM -0800, Greg Stein wrote: > > > Doing a quick search, here is what I found about the proxy stuff in the > > > past > > > six months: >... > It's somewhat of an indicator of the thrash in the main codebase over the > last six months, no?
Yes, but that is beside the point. The codebase is thrashing, and we have to spend energy carrying along the proxy code (despite it not working well or right). >... > > To me it clear it should be in it's own repository, and it's also clear > > nothing can be > > clearly settled until new code is written/submitted. Until then, nothing > > _very_ usefull > > will happen. Exactly! We need volunteers. Talking about this stuff, submitting a patch whenever it comes up, etc, is not going to move us to a final proxy. >... > 0) drop mod_proxy as an apache module, supported or unsupported I don't think we need to go to this extreme; I don't think the code is in *that* bad of shape. > 1) move mod_proxy out of the core until it's at least beta quality > > 2) drop the whole existing mod_proxy and start over in a new CVS module until > it's ready > > 3) do 1) and 2) both This is for the proxy developers (who would they be?) to decide. I think it should be moved out of the core to httpd-proxy/ (e.g. part of the httpd PMC? maybe a new proxy PMC?). If those people want to use the existing codebase, then great. Start a new one? By all means. My personal vote is to just see it moved, get more committers for the new repository, and see that its development gets some real traction. Cheers, -g -- Greg Stein, http://www.lyra.org/
