×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Tue, Jan 23, 2018 at 8:49 AM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:
And I'd say avoid starting a separate JVM for every single Java call unless you have overwhelming reason to do so.
Well, you make it sound like each "single Java call" is a small amount
of "real work", akin to a typical function or procedure call, and in
those terms, it certainly feels like a whole JVM just for each of
those is a ton of overhead.
But what I think Richard is describing is a completely different way
of working. Roughly speaking, if there's a component of an application
which is hard to build in RPG but easy to build (or already built) in
Java, then instead of making the bulk of the application in RPG and
only "calling out" to Java for that component, he's going whole hog
and building the entire application in Java.
So, it seems to me that both of you are avoiding firing up a separate
JVM for every (small) function or procedure call.
John Y.
As an Amazon Associate we earn from qualifying purchases.