PlatformAPIPages
JOSystem
(pronounced JOE-System (anyone else having a "peanuts" flashback?))
The name for the actual OS part of JOS, consisting of JOSCore and JOSExtensions and running in parallel with the Java API's.
(ahem) JOSCore (aka org.jos.core.*) will be used to implement the Java API's. No normal application (i.e. non-JOS SystemUtility) should ever
access the org.jos.core.* API.
JOSExtensions will likely be used to implement javax.* packages and additional SystemUtilities.
-- AveryRegier (17 Feb 1999)
I think we have a naming conflict here, by JOSCore I mean the minimum Components for JOS to run on the JOSBox and still be considered an OS, and JOSExtensions being all the other stuff people need/want for it to be a successful OS. I didn't mean the packages, sorry for the confusion.
-- DigiGod 99.02.17
JOSCore
I've been doing some blitzekrieg-type research on various things and it got me to thinking about what exactly would go in JOSCore. Here's a list (feel free to edit or comment) of what I think should be in JOSCore:
- Access to the JOSBox (duh)
- A meta-mechanism for "startup" stuff (what JOSExtensions to load, say from an "config.xml"-type file) (note: needs to be a metamech since JOS might not have a fs under it from which to read said file)
- Security and Process Managment (responsible for spawning new processes like JADE)
- A framework to (dynamically?) plug in JOSExtensions (possibly as Servlets)
The JOSBox would start and load JOSCore, JOSCore would use the metaconfiguration mechanism to "build" itself with the appropriate extensions (via another metamech) and then load JADE in a sub-process (as it is an application of JOS and doesn't have to be used but most likely will be. I'll leave it up to the configuration system to tell JOS to load it or something else) so the users can run pong or whatever it is users do.
I think thats the base functionality needed. Everything else would be an extension, some required in the sense that almost everyone uses them but still an extension (as per the MicrokernelPattern)
-- DigiGod 99.02.23
You might want to picture ultimate JOS architecture like this, from the bottom up:
|
JOS kernel
|
|
Java virtual machine
|
JOSBox
|
JOSystem
|
|
Java Platform
|
|
applications
|
In order to present java. and javax. to pure bytecode applications, there must be a layer between these class libraries and a Java virtual machine. This layer is JOSystem.
It is possible to maintain different implementations JOSystem, while consistently developing one implementation of java. and javax. packages for each Java platform. -- GilbertHerschberger (17 November 1999)
|
Content of these pages are owned and copyrighted by the poster.
|
|
Hosted by:
|
|