in reply to Java::Inline vs Java::Import Opinions

what about creating a extra perl process that communicates with your CGI app; that perl process will hook with JNI via Inline::Java. This way maybe you can control or profile more easily, and at the same time you don't compromise your apache process. If the extra perl process dies, well your restart it, or better let it restart itself every 100 calls or so.

cheers --stephan
  • Comment on Re: Java::Inline vs Java::Import Opinions

Replies are listed 'Best First'.
Re: Java::Inline vs Java::Import Opinions
by Dooz (Novice) on Jun 04, 2007 at 14:06 UTC
    That is a nice idea Stephan. Have a separate process to test out Inline::Java with JNI and Java::Import and see what works better. Then the older code can stay as it is.

    I'm guessing the IPC bundle is the best bet for communicating with the other process? Sorry for the newbie questions, this particular problem is stretching my Perl "skills" to the limits.
[reply]

In Section Seekers of Perl Wisdom