Right, but mod_proxy cuts an httpd-2.x-proxy release with binaries.
Along with any other modules outside the core modules, I presume (one
rollup release). Mod_rewrite is a contender. I think this is the current
thinking.
I think cutting a release is what's different here from mod_perl.
Chuck
On Thursday, April 19, 2001, at 03:48 PM, Graham Leggett wrote:
> Chuck Murcko wrote:
>
>> c) Treating mod_proxy maintenance as NOT tied to httpd, mod_proxy
>> development as running on its own release cycle, mod_proxy code has its
>> own cvs module (hey, we can start module-2.1 now, right), and is
>> released with httpd distribution. Note that this may require some
>> reintegration at each httpd release (and more work than b).
>
> ie exactly like APR and APR-util.
>
> I like this one - hacking at the proxy does not spoil things for httpd,
> the the httpd people get to have a builtin proxy without any extra work
> on their part.
>
> All that remains is that the maintainers of proxy check in a stable
> version of proxy into httpd when new features become stable, or bugfixes
> are found.
Chuck Murcko
Topsail Group
http://www.topsail.org/
