Bad news for me and many others since without AJP support included in 2.0.x, users will still require to have mod_jk to link there HTTPD to Tomcats.
Could we hope the dev team to relax the situation for mod_proxy/ajp in future 2.0.x release, since Graham, Mladen and Jean-Frederic works hard to make mod_proxy as stable as possible even now with AJP support ? Regards On Thu, 02 Sep 2004 08:59:55 -0500, William A. Rowe, Jr. <[EMAIL PROTECTED]> wrote: > > > At 07:55 AM 9/2/2004, Henri Gomez wrote: > >Should we see the works on mod_proxy and ajp support in the upcoming 2.0.51 ? > > No, not in 2.0.51 (and to your following question of 2.0.x later > releases, also likely no.) > > Yes, in 2.1.0. > > It was commented that mod_proxy is becoming quite stable - bug > fixes are being backported but in general, a good number of the > developers are focusing their efforts at getting the first 2.1.x > unstable release out the door, and working on mod_cache and other > issues to get a 2.2.0 general release out the door. > > By releasing 2.1-dev several times, those users interested in > proxy_ajp and other new proxy features can help shake out the > issues before this code is branded 2.2. > > The focus for 2.0.x is bug fixes, and 2.2.0 is the next major > feature release. It's evens/odds versioning between stable > and unstable development code. With the change, the API of > both 2.0 and 2.2 should be stable for developers. The changes > in mod_proxy don't lend themselves to binary compatibility > with any third party extensions developers had built around > 2.0 mod_proxy. > > Bill > >
