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

"The focus on orthogonally persistent systems (i.e. systems where the persistence of data is orthogonal to all other properties of the data [Atkinson and Morrison 1995]), stems from a desire to build systems that elegantly unify the divergent database and programming language paradigms."

From The Transactional Object Cache as a Basis for Persistent Java System Construction

Persistent OSes provide one object environment abstracted from memory and persistent storage. A named object has state when referenced regardless of its actual position (in memory or on disk) the moment before it's called on. The OS provides virtual memory maintaining the state of all objects, until consumed or destroyed.

The benefit of this system is to abstract from both objectbase and Encapsulation or Activation, providing a type free environment.

Persistent OSes must be distinct from distributed persistent OSes. The abstraction from disk and core should not be blurred into a less determinate abstraction over memory, disk and network. Network communications among host nodes are distinct from object 'existance' so that the latency, overhead and potential for failure inherent in communicating does not become a possible property of the persistent object space.

Grasshopper is an orthogonally persistent operating system. -- JohnPritchard

OK, I have read through some of the Grasshopper papers - this is very interesting, it sounds like cellular automata (and other things I like much). Also, others have proven already that a Java OS built as a conventional architecture can be implemented quite fast and with all necessary device drivers (see OSKit ref in the readings). You wont hear pragmatist arguments from me, but is there a consensus within the JOS kernel population to aim at orthogonal persistence, and if so, what is happening? And a question from an OS amateur: could one build an orthogonally persistent OS on top of something like OSKit, thereby reusing tons of existing driver code? -- RalfStephan



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