Ryan is absolutely correct.  On my way to JavaOne this year, I sat down on
the plane and did a careful reading of the Java Virtrual Machine
Specification, 2nd Edition, and came up with an overall strategy for sharing
class definitions, but not static class data, between processes.  You *can*
do this and still remain 100% compatible with the JVM spec.  My notes are at
home on how to do this, but I'll try to get the design posted on the Wiki in
the next few days.

While I was at JavaOne, I spoke with one of the original members of the team
that wrote JavaOS.  I ran my ideas by him, and he told me they were
reasonable.  He no longer works for Sun, and would have liked to help with
the project, but he is too tainted with Sun code.  :)

Regards,
Avery J. Regier



> -----Original Message-----
> From: Ryan Heise [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, July 20, 1999 10:37 PM
> To:   [EMAIL PROTECTED]
> Subject:      Re: [JOS-Kernel] Construction of a new Java Operating System
> 
> Cliff Baeseman wrote:
> > 
> > Ok here is the deal how do you plan on sharing the classes between
> multiple
> > application instances as shared without reloading the classes. You still
> > have to create the classes in memory to allow proper instancing. The
> classes
> > have to run in your application instance in any case. This goes for jit
> our
> > jvm makes no difference. You could share the classes right now if you
> wished
> > to but how do you keep the data state within those classes?
> > 
> > That is the real question, the answer is that you cannot!
> 
> We can. The JVM can keep static class data separate from the class
> definition itself, thus allowing the classes to be shared and static
> data to be kept separate per process.
> 
> I think the first of the documents referred to by Avery also answers the
> question.
> 
> -- 
> Ryan Heise
> 
> http://www.progsoc.uts.edu.au/~rheise/
> 
> _______________________________________________
> Kernel maillist  -  [EMAIL PROTECTED]
> http://jos.org/mailman/listinfo/kernel

_______________________________________________
Kernel maillist  -  [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel

Reply via email to