| Content of these pages are owned and copyrighted by the poster. | |
| Hosted by: |
|
Q: What is the JOS platform?
The JOS platform defines the interaction between applications, such as e-mail, and subsystems, such as the device driver manager. It includes the security model to control an application's access to the kernel and devices.
Q: How is the JOS platform different than Java platforms?
JOS(tm) and Java(tm) have a different set of assumptions. The JOS platform is far more comprehensive than the Java platform. The JOS platform fills in subsystems that Java assumes are provided by the native OS. Since the Ultimate JOS has no native operating system, the JOS platform cannot assume these services are automatically provided by a foreign OS.
These platforms are related. The JOS platform provides a full implementation of each Java platform. You can run any pure Java application.
Q: What tasks will my JOS application delegate to the JOS platform?
Like a Java application, a JOS application delegates the management of the OS file subsystem to the JOS device manager. JOS applications can benefit from greater efficiency than a Java application as device subsystems are event-driven from the ground up. A JOS application can listen for data from a device rather than poll the OS file subsystem for additional data.
The JOS platform provides additional class libraries for creating a new user and the rest of account management. It provides class libraries for maintaining the system-wide and network-wide configuration of operating system(s). It provide routine diagnostic tools and other subsystems to maintain the stability of the operating system.
A transitional JOS has a full security model separate from the native OS. JOS provide a security model for operating systems that, traditionally, have little or no security. Since JOS uses its own file subsystem on top of a native OS, native program will not be able to read or write JOS-specific data. JOS uses a model of services that share data with native program through IPC, as well as import and export. With your FTP or HTTP server running under JOS, you can download files from both your native OS and JOS.
The JOS application must delegate the creation of a domain to the JOS platform. A new domain is provided by JOS for each security session. JOS supports multiple concurrent domains. When a program is complete, the domain is destroyed. When the primary domain is destroyed, JOS "reboots" a new primary domain, reboots a machine, or halts the processor.
Q: Why should JOS use the JavaOS as a model, even when the Java OS is discontinued?
JOS benefits from the experience of others. The JavaOS is a great place to start when defining something as complex as the JOS platform. The JavaOS is well documented. JOS will grow. JOS is something different. JOS is not a clone of the JavaOS. While starting with the JavaOS, JOS is always subject to meaningful innovation.
Q: Where are the class libraries that define the JOS platform?
The JOS platform is a work-in-progress. Very few of its mechanisms are defined well enough to put into code. This is expected to change, as JJOS/decaf nears completion.
Q: How do I propose a class library for the JOS platform?
A minor recommendation might be posted on the architecture mailing list. A major proposal should be written up and posted to (1) your own website, or (2) a JOS Wiki page. After writing your proposal, call attention to it on the architecture mailing list. Please send us its URL!
When writing a proposal, "Proposal" should be the last "word" of the name of your JOS Wiki page. A proposal for a new device architecture, for example, might be called DeviceProposal (or MyNameDeviceProposal).
| Content of these pages are owned and copyrighted by the poster. | |
| Hosted by: |
|