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

That's very interesting. 

Though I've never implemented nor had a need for a solution like this, I 
wouldn't
have wanted that as a solution (accessing internals of one job/JVM from 
another) because 
although it gives me power, it violates some isolation principles that I 
sort of prefer. 

I would have instead felt comfortable with the level of support granted by 
the
direct connect to the server using whatever appropriate communications 
mechanism.

That gives me a good insights into your mind/solutions.
What I hear in general is this? This fair?
        "more power, fewer constraints, if I break the system or the 
application
        so be it, but there's no point in this machine if I can't leverage 
it for my solutions"

Of course, there is big market demand, which I suppose is driven by less 
competent developers, 
more bugs in fearful/pounded IT departments and tighter security 
requirements, who request in the 
other direction. 

Obviously, solutions to those things exist, but so do they cost money to 
do them right.
Its always an interesting balancing act as to what is needed relative to 
what can be sold/afforded.

Thanks!




"The stuff we call "software" is not like anything that human society 
  is used to thinking about. Software is something like a machine, and 
  something like mathematics, and something like language, and 
  something like thought, and art, and information... 
  but software is not in fact any of those other things."
Bruce Sterling - The Hacker Crackdown

Fred A. Kulack - IBM eServer iSeries - Enterprise Application Solutions
ERP, Java DB2 access, Jdbc, JTA, etc...
IBM in Rochester, MN  (Phone: 507.253.5982   T/L 553-5982)
mailto:kulack/us.ibm.com   Personal: mailto:kulack/magnaspeed.net
AIM Home:FKulack  AIM Work:FKulackWrk 
MSN Work: fakulack/hotmail.com (replace email / with @)