> What is really needed is a pre-started jvm. When you start up a java
> process, the jvm will fork, and the child will su to you and proceed as
> normal. I don't know exactly what the jvm is doing when it is taking
> all that time starting up so I don't know how useful this would be.
I like this solution, though I don't see the details.
My guess is that part of the startup time is just that java
has to uncompress the classes zip file, which is big. The
scheme above would avoid the uncompress.
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
