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" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
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.



This message is intended only for the use of the person(s) listed above as the 
intended recipient(s), and may contain information that is PRIVILEGED and 
CONFIDENTIAL.  If you are not an intended recipient, you may not read, copy, or 
distribute this message or any attachment. If you received this communication in 
error, please notify us immediately by e-mail and then delete all copies of this 
message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the 
Internet is not secure. Do not send confidential or sensitive information, such as 
social security numbers, account numbers, personal identification numbers and 
passwords, to us via ordinary (unencrypted) e-mail.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to