> > should be very amenable to the Apache 2.0 infrastructure. I would not
> > personally spend any time trying to make mod_jk or mod_jserv work in a 2.0
> > environment, when the future is clearly in a different direction.
>
> Since I believe in a different future and direction, I'll spend the
> time to make mod_jk and tomcat3.2 ( and the future 3.3 ) work with
> Apache2.0.
In other words - feel free to follow the direction you like, but please
let people who have a different opinion spend the time on what the feel is
the future !!
I'm not telling anyone to "spend any time" on mod_jk if they don't feel
it's a good protocol and a great idea - I offered my help to make tomcat
3.2 work with Apache 2.0. I hope other people will help - and it will be
useful for those who upgrade to Apache 2.0 ( and probably part
of the future ).
Mod_jk supporst IIS, NES, AOLServer, Apache1.3 - there is no reason not to
do the same for Apache2.0.
It supports AJP12 ( from mod_jserv ), Ajp13, JNI - there is no reason not
to support the mod_webapp protocol.
It can be configured with the native config systems of Apache, NES, IIS -
it'll be even better when it'll be able to use the web.xml too.
Costin
