jk2 is a refactoring of jk and is much more powerfull.
even if it works with apache 1.3, jk2 has been developed with apache 2.0 in mind, and is better suited for multi-threaded servers like iis, nes/iplanet. it can also be embeded in other applications and used from java.
jk2 improves the modularity and has a better separation between protocol and physical layer. as such jk2 support fast unix-socket, and could be extended to support others communications channels. it is better suited for jni and may use (in a future version) jdk 1.4 nio.
there is additional support for monitoring, similar with jmx in java. a module similar with mod_status is provided, and additional adapters can be used to interface and provide status and runtime configuration. .
the configuration has been changed to follow the component models. multiple configuration sources can be supported ( in additon to file ) providing better integration with the embeding application. the config layer uses the management layer apis and it can support persistence for changes done via runtime configuration.
another feature is the jni mode. jk2 can be used as a jni library and provide access to native features to java. for example it provides access to shared memory ( used for config and monitoring in a multiprocess environment ), unix domain sockets. it can also provide access to signals, chuid, win registry. all using the same communication mechansim, and supporting both in-process and out-of process modes.
 are there alternative ways to connect apache and tomcat? |
