Home   Info   DevZone   Wiki  
UsersWeb  |  MainWeb  |  InfoWeb  |  DevZoneWeb  |  SupportWeb
JOSDesignIssues ] [ not logged in ] [ Web: Imported ] goto:  options
[ get info on or edit ] login or new user ] [ list of topics, hubs & nodes, or recent changes ]

PlatformAPIPages


There's been a lot of heat on the MailingLists over the design of JOS, I created this page to help us sort them out. --DigiGod
NOSHADE SIZE=1>

The JosPlatform approach

This idea originally came up on the MailingLists. ( from: DmitryBisikalo )

In this approach we seperate into two main factions, one working on the JosBox, the other working on JOS.

The JosBox would be virtual hardware on which the VM rests, on top of that is JOS itself. JOS would control the computer's hardware via the JosBox and the Applications could run blissfully unaware of the OS below.

Basically: JosPlatform = JosBox + JOS

This approach would allow us to start development faster sense we would know almost exactly what we have to do.

--DigiGod


I agree with DigiGod, There should be two layers of the JOS System... The upper application level, and the lower arch. level. This would also allow easy implementation (port) of a JOS System that runs on top of other operationg system, such as Windows, or Solaris. And allow for communication between the two.

I would also add that the upper level and lower level should conform to the standard Java API in ALL ways, so that software not designed for JOS, could be run in JOS. This would have to include the JRE/JDK methods of extension, and property managment.

--BrillPappin


NOSHADE SIZE=1>

Your non-clone design idea here




Content of these pages are owned and copyrighted by the poster.
Hosted by: