tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <wbar...@wilshire.com>
Subject Re: JK Todo List
Date Fri, 08 Oct 2004 15:38:02 GMT
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....

----- Original Message ----- 
From: "Mladen Turk" <mturk@apache.org>
To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Sent: Friday, October 08, 2004 4:28 AM
Subject: JK Todo List


> Hi,
>
> Here is my Todo List for JK:
>
> - Documentation
> - Use Apache coding style (already done 90%) using simple .indent.pro
> - Fix all 64/32 bit compatibility issues.
> - Backport IIS Worker thread pool from JK2.
> - Backport some ajp messaging stuff from proxy_ajp (mostly performance).
> - Backport shared memory from JK2 for load balancer worker.
>
> What's more important:
>
> - Documentation
> - Put the JK2 in 'maintainer' mode.
> - Inform our users about that decision.
> - Inform out users that we are still in native<->tomcat business :)
>
> Long term plans:
>
> - Documentation
> - Backport unix sockets from JK2
> - Backport JNI from JK2 with lots improvements.

I agree with Remy here.  It's not worth doing with the existing codebase. 
If you want JNI, you need to do it again from scratch.

> - Use 1.4 API on Java side
> - Add full AJP14 protocol support

-0.  This is what proxy_ajp is for.

> - Add encryption and compression to AJP protocol
> - APR-ize JK

I'm very strongly -1 on requiring APR in JK.  The main purpose of JK is for 
Luddites (myself included) who are still using Apache 1.3.

>
> Regards,
> MT.
> 



Mime
View raw message