Oracle has developed a virtualized JVM for their various web products.
It puts all the shared, read-only stuff in one layer and all the private
read-write stuff in another layer. It allows each client session to
have effectively their own private JVM with something like 20KB overhead
per ses
> The problem is that the connection to the X display happens when the AWT
> native library is first loaded. It's a single connection that is used
> through the life of the JVM. As currently structured, the AWT won't let
> you associate different objects with different X connections. It would
> ta
Sounds what we need is the old UNIX sticky bit put back into Linux. The
sticky bit was a file attribute that told the Kernel that the
application should stay in cached for some period of time after it was
initially loaded. Way back when, UNIX did this and things that got hit a
lot like editors (vi
