Mladen Turk wrote:
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 still don't see benefits in JNI as a transport for JK. Only trouble (no matter how I look at it, it seems like it would actually make the whole system much less robust) and complexity.
Did I miss something ?
- Use 1.4 API on Java side - Add full AJP14 protocol support - Add encryption and compression to AJP protocol - APR-ize JK
Rémy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
