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!
You have to pool the JVM it is the only way to provide speed and efficency
and application process seperation.
Cliff
-----Original Message-----
From: Regier Avery J <[EMAIL PROTECTED]>
To: '[EMAIL PROTECTED]' <[EMAIL PROTECTED]>
Date: Tuesday, July 20, 1999 4:07 PM
Subject: RE: [JOS-Kernel] Construction of a new Java Operating System
>> -----Original Message-----
>> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
>> Sent: Monday, July 19, 1999 6:37 AM
>> To: [EMAIL PROTECTED]
>> Subject: Re: [JOS-Kernel] Construction of a new Java Operating System
>>
>> From: [EMAIL PROTECTED]
>>
>>
>> On Mon, 19 Jul 1999, Ryan Heise wrote:
>>
>> >Cliff Baeseman wrote:
>> >
>> >> JOS is also based on a single instance JVM design. This is a very poor
>> >> design in my opinion.
>>
>JJOS is *currently* based on a single instance design. In time, though, it
>will come to support Multiple Java Processes while still having the
>advantages noted below:
>
>> >
>> >It allows you to share 15 megs of system classes between applications.
>> >It allows you to have one thread scheduler across all applications. It
>> >allows you to have one garbage collecter and memory manager across all
>> >applications. There are a few other optimizations that are possible.
>>
>> What about possibility of multiuser usage of such an OS (from the
security
>> point of view?) Or is this JOS project positioned only for client
>> platform?
>>
>>
>> Dmitry M. Golubovsky
>> St-Petersburg, Russia
>>
>>
>The design we want to get to eventually will allow us to enforce security
>and memory limits on Java Processes while still only loading and compiling
>class bytecodes once.
>
>Here are some good pages to read and follow the links of on the Wiki:
>http://jos.org/wiki/view/Main/WhyMultiProcessJVM
>http://jos.org/wiki/view/Main/JOSCoreProjectUpdate
>http://jos.org/wiki/view/Main/MultiUserGroup
>
>-- Avery J. Regier
>
>_______________________________________________
>Kernel maillist - [EMAIL PROTECTED]
>http://jos.org/mailman/listinfo/kernel
>
>
_______________________________________________
Kernel maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel
