On Thursday, May 10, 2001, at 01:40 AM, Eli Marmor wrote:
* possibly to fold this into a later release (1.3.20++?) currently being maintained as a separate patch
Now - or never.
Likely never, see below.
In a separate message to "another mailing list", under the title "Proposed
Code Freeze for 1.3.20", William A. Rowe, Jr. wrote:
can we please freeze development now excepting fixes to absolutely broken stuff?
So it's urgent.
Is it possible to do it now?
After the patch has stabilized, is there a reason for new-httpd to insist
on including only the old mod_proxy in 1.3.20, and only HTTP/1.0, with no
support for HTTP/1.1?
Yes. new-httpd voted not to include the HTTP/1.1 patch a year or so ago because it would require more effort and testing to include with 1.3.x than the group was willing to do in light of development on 2.0.
So it's packaged separately. I'm putting it under cvs control in httpd-proxy module, just figuring out the order so I have working Win32 and correct history. There are a couple of small patches to add to this mix.
New packaging will be a small patch & archive w/new mod_proxy sources. Think of mod_proxy as a subproject of 1.3, even though no one's actually used those words yet, to my knowledge.
I'm hoping to do a "1.3 rollup source release" including the newer mod_proxy as part of testing the mechanism for 2.0, but I am swamped with my real job for about a week, so expect this to trickle in, but get there by the time we cut a real httpd release.
Chuck Murcko Topsail Group http://www.topsail.org/
