Initial import of ap-jk-3.2.1, the next generation connector for accessing
authorjwise <jwise>
Thu, 29 Mar 2001 19:34:18 +0000 (19:34 +0000)
committerjwise <jwise>
Thu, 29 Mar 2001 19:34:18 +0000 (19:34 +0000)
commit85998e536ff49bfc310c66eea332518c796f25f6
treeb3571d2de93330f67cffa7d1505b08e45961cf54
parenta486338bde66b26e723135d8ace0b1a6030dc718
Initial import of ap-jk-3.2.1, the next generation connector for accessing
Jakarta Tomcat of JServ from Apache.

Some more information:

What is mod_jk?

mod_jk is a replacement to the elderly mod_jserv. It is a completely
new Tomcat-Apache plugin that handles the communication between
Tomcat and Apache

Why mod_jk?

Several reasons:

mod_jserv was too complex. Because it was ported from Apache/JServ,
it brought with it lots of JServ specific bits that aren't needed
by Apache.

mod_jserv supported only Apache. Tomcat supports many web servers
through a compatibility layer named the jk library. Supporting two
different modes of work became problematic in terms of support,
documentation and bug fixes. mod_jk should fix that.

The layered approach provided by the jk library makes it easier to
support both Apache1.3.x and Apache2.xx.

Better support for SSL. mod_jserv couldn't reliably identify whether
a request was made via HTTP or HTTPS. mod_jk can, using the newer
Ajpv13 protocol.
www/ap-jk/Makefile [new file with mode: 0644]
www/ap-jk/files/patch-sum [new file with mode: 0644]
www/ap-jk/patches/patch-aa [new file with mode: 0644]
www/ap-jk/pkg/DESCR [new file with mode: 0644]
www/ap-jk/pkg/PLIST [new file with mode: 0644]