On Wed, 22 Jan 2003 21:00, Jakob Praher wrote:
> saw a "Peter Donald" as a member of the Isolation API JSR expert group -
> Is it you?
Yep. Though I am no expert - all the rest of the group were way smarter than
me ;)
> I like the current version, and am very curious about the impact on
> large server installments.
Nice reliable isolated environments where one bad thread can't muck others up.
ie Imagine the ability to put each servlet (or each web-app or EJB or
whatever) in a different isolate. No longer will a single badly written
EJB/servlet/whatever take down a JVM or suck up oodles of resources.
In the future more resource management will come to the JVM and you will be
able to do sorts of good stuff. It wont be fully utilized till jdk1.6 but it
will be great to have it in place by then. Phoenix was sorta built to
natively support all that sort of stuff transparently when it becomes
available in the wild.
> Also want to play with it on the jikes rvm (which is a lovely vm for
> testing purposes).
I wrote a JVM once just for kicks and then watched the www.jos.org people
write a jvm/OS in java. It was kinda fun for a while ;)
> Especially class caching could be a very hot
> topic.... although sometimes tricky to implement.
Yep. IBMs JVMs do wonders with this and I believe most of their research is
online if you are interested (sorry dont know url).
> > A few people have asked me to describe what the difference is between
> > coarse and fine grained components. However I don't think there is any
> > hard and fast rules for that.
>
> I think so too. I see coarse grained components as subsystems, that
> appear a kind of closed to their environment and other systems. Although
> they can depend on another.
yep.
> Coarse grained for instance could mean then
> - very few data is shared (better no data)
thats a good point.
> Don't know that much about the ongoing blocks discussion (especially
> from cocoon-committers), but perhaps blocks (which appear to me as a
> kind of subsystem) could be hot deployed via such a construct - as
> inter-block communication is rather scarce compared to inner-block
> communication - but as I said : don't know that much about the
> requirements here.
The terminology is confusing. Cocoon blocks refer to something different from
phoenix blocks. Cocoon blocks refer to what Phoenix terms applications and
Phoenix blocks are somethign different again. There is some mediated
inter-application communication that is mediated by JMX (if you configure
your kernel that way). It is just painful to do atm - we weren't sure until
recently how tightly to couple to JMX so we shied away and thus made things
difficult. It should be easier to do this in the future.
--
Cheers,
Peter Donald
'Most men would rather die than think. Many do.'
Bertrand Russell
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
