Costin Manolache wrote:
In jk2 we use ajp13 for all channels, including JNI. That allows us to reuse
the buffers and avoid object allocations from C - which improves a lot the performance of the code ( we also avoid a lot of expensive calls, etc ).
Same technique is also used (AFAIK) in mozilla bridge.
Do you mean "ajp13" channel would work with in-process worker?
Let me rephrase my initial question. I am interested in Tomcat executing in-process. If JNI worker cannot be used, what alternative do I have to run Tomcat in-process? Is JNI worker permanently out or will be re-enabled in the future (what's the timetable?)Is JNI worker intentionally disabled, or am I misinterpreting the code?Yes, the jni worker shouldn't be used.
I could fix jk2_jni_worker_service function with some guidance, but is
there a similar implementation gap in Tomcat 4 Java classes?
In case I am out-of luck with in-process Tomcat <g>, what is the highest performance alternative for a Web server to talk to Tomcat 4?
Thanks for your help!
Alex
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
