jeff at zeroclue.com
Wed Apr 7 19:07:06 CDT 2004
I was going to suggest a solution along these lines using Tomcat. You
want to avoid starting up a JVM as much as possible, it's an expensive
thing to do and if I understand things correctly you can't get much
benefit from a JIT unless your JVM is left running...
On Wed, 7 Apr 2004, Austin Schutz wrote:
> On Wed, Apr 07, 2004 at 10:45:30AM -0700, Chris Dawson wrote:
> > I have been using perl SOAP for a while now and really like the
> > simplicity compared to other toolkits. I have a project, however, where
> > I need to use a third party java library (.jar) to do work backend
> > work. I was thinking of using Inline.pm to run the java code, and then
> > have this perl wrapper also manage the SOAP interface, calling into the
> > java when necessary. The java is actually going to run a subshelled
> > compiled C program... This may be a vague question, but I will ask it
> > anyway. Does anyone have experience using perl in this way, in other
> > words, to manage a java interpreter in a program which will sit as a
> > daemon for long periods of time? Are there tricks I can use to minimize
> > startup time of the java interpreter? Is this generally a bad idea?
> > For example, my code will likely do something as follows: run the perl
> > program, bring up the SOAP server, wait for a command; upon a start
> > command, start the JVM and execute until the stop command is processed.
> > Any thoughts?
> This is probably more work, slower, and less reliable than using java
> soap tools with a java web engine like apache axis.
> If you want perl too, maybe run two webservers on the same box,
> and write glue code where you need to integrate java <-> perl.
> *shrug* that's the road I would probably follow.
> Pdx-pm-list mailing list
> Pdx-pm-list at mail.pm.org
More information about the Pdx-pm-list