RE: system-wide JVM (threads) Was: Friendly co-existance

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: Fred Kulack
> 
> Hmmm....
> Indeed, would be pretty cool.
> But, the usual answer for this type of request would be something like
> "use threads", right?

I'm not sure what you're saying here, Fred.  What I want is to be able
to start an application or call a class from RPG and in either case use
a JVM that is already started.  I would then have access to all the
objects in that JVM (which I could share among jobs through a static
member in a class).


> I have my own knowledge and opinions about why threading is
easy/difficult
> and what its
> suited/not-suited for, but this group is a bit emotionally charged, so
> I'll keep those to myself here.  8-)

Chicken.  <smile>  Also, I'm not the one insisting on a threading
answer.  I've explained my requirements in the previous paragraph.  I
don't care how it's done, it would be a killer feature.


> In general, what are you opinions on the threads type of answer?
> Too MUCH sharing and too complex of synchronization/coding/debug of
those
> items?

I have no problem with threading and synchronization.  Those of us who
program servlets deal with it all the time, and in fact I've developed a
servlet proxy class that gets around all of those issues.  It would be
nice if there were a context associated with my job that I could access
easily, much like there is an HTTP session that I can access for a
browser session.  That would allow me to keep track of job-specific
information.

I guess I'm not understanding what the issue is.

Joe