> Well, why not do the same as we've done for APR? I don't see why mod_proxy > can be "bundled" in the same way can't it? It seems to make sense as both > an included "entity" and a seperate project. > I can go with that. Ship mod_proxy with http server releases but maintain it as a seperate project. I would really not like to see it supported like, say, mod_perl or mod_dav in Apache 1.3 (i.e., not bundled with an http server release). Bill
- Re: [VOTE] mod_proxy in? William A. Rowe, Jr.
- Re: [VOTE] mod_proxy in? Graham Leggett
- Re: [VOTE] mod_proxy in? David Reid
- Re: [VOTE] mod_proxy in? Graham Leggett
- Re: [VOTE] mod_proxy in? David Reid
- Re: [VOTE] mod_proxy in? Jim Jagielski
- Re: [VOTE] mod_proxy in? Chuck Murcko
- Re: [VOTE] mod_proxy in? Chuck Murcko
- Re: [VOTE] mod_proxy in? Greg Stein
- Re: [VOTE] mod_proxy in? Chuck Murcko
- Re: [VOTE] mod_proxy in? Bill Stoddard
- Re: [VOTE] mod_proxy in? William A. Rowe, Jr.
- Re: [VOTE] mod_proxy in? Graham Leggett
- Re: [VOTE] mod_proxy in? Jim Jagielski
- Re: [VOTE] mod_proxy in? rbb
- Re: [VOTE] mod_proxy in? Graham Leggett
- Build system that could integra... Sean Chittenden
- Re: [VOTE] mod_proxy in? Graham Leggett
- RE: [VOTE] mod_proxy in? Ian Holsman
- Re: [VOTE] mod_proxy in? Jim Jagielski
- Re: [VOTE] mod_proxy in? Chuck Murcko
