Over all, I don't, personally, think that it's worth trying to build on the existing Jk code base. However, if you have an itch....
Well, we deceased JK2, for Apache2.1 we have proxy_ajp. Until Apache2.1 becomes the only server around the net, I'll stick with JK for all those not running my preferred web server :).
Right. However, I think JK 1.2.x needs some level of stability. So APR, large architectural changes, etc seem bad ideas. Of your list, I think documentation (yah !) and the Unix sockets backport would be good (if not too complex), but that's about it. Modifications to the Java side is something independent.
I think it would rise the stability, but introduce new problems like building APR, etc.. so you are probably right. We'll see.
For the long term, if you would want better support for the other servers, you can start a 100% APR replacement for JK 1.2 (I think it was a bit like your mod_ajp) if you want to.
I'm surely do. The IIS6 support is something to chase :).
MT.
smime.p7s
Description: S/MIME Cryptographic Signature
