Günter Knauf wrote:
As things are now standing, mod_jk will continue support for the
following servers:
apache 1.3.x, apache 2.0.x, IIS, Netscape. (Domino is down I think,
because nobody cares, thought).
ok, fine. BTW. for Netscape on NW applies the same as for Apache 1.3.x.
Sure ;).
Netscape iPlanet/SunOne is supported, others are fully supported.
Apache 2.1/2.2 has mod_proxy_ajp with the active development, and
surprisingly stable :).
what's missing for 2.0.x? cant we just compile it for the 2.0.x series too?
Well, you can try, and it will probably build, but couple of things are
missing:
1. Shared memory support
2. Waitable resource pools.
So, it can be used, but not for the production thought.
Also, proxy protocol support is different in 2.1, so not sure
if it comply to RFC if used inside 2.0.
thanks very much for the update - although one point you didnt mention:
what was the reason that you stopped with mod_jk2?
Yes I did (It was BTW not solely my idea - browse the archive).
jk2 was not as stable as jk, particularly on apache 1.3, and IIS.
We had new mod_proxy, and maintaining three connectors would be way
too much considering the number of active developers. We had
reasonably stable product (jk), that needed just a little bit
push-up with all the good things that we know how and why worked
in jk2.
Regards,
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
