On Oct 7, 2005, at 11:45 AM, Michael Peters wrote:
Well, since the mod_perl processes are already somewhat big (although
not too big), memory is a consideration. But mainly it's because I
don't
know that much about it...
For instance, this line from the Inline::Java docs:
Note: Inline::Java only creates one virtual machine instance.
Therefore you can't use JNI for some sections and client/server for
others. The first section determines the execution mode.
It seems that the mod_perl processes would load Java as a shared
object,
but what about cron jobs? In the application, there are several perl
scripts that run outside of apache that do some additional processing
on
work queues, data caching, etc, that all need to use Java. Does using
the JNI allow this?
Yeah, that section in the docs means that you can't use the two
different modes in the same program. You can pick and choose the mode
in different program, though.
You might get better concurrency out of your server by switching to JNI
too, since they wouldn't have to share the same JVM.
-Ken
