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.

Regards,
Graham
-- 
-----------------------------------------
[EMAIL PROTECTED]                "There's a moon
                                        over Bourbon Street
                                                tonight..."

Reply via email to