Maynard R Johnson

US Patent:

6301582, Oct 9, 2001

Filed:

Mar 30, 1998

Appl. No.:

9/050821

Inventors:

Maynard Paul Johnson - Rochester MN
Steven Jay Munroe - Rochester MN
John Gerard Nistler - Rochester MN
James W. Stopyro - Rochester MN

Assignee:

International Business Machines Corporation - Armonk NY

International Classification:

G06F 1700

US Classification:

707103

Abstract:

The preferred embodiment of the present invention facilitates the creation, storage and interaction of persistent objects using single level storage semantics on commodity systems. The preferred method and apparatus utilize a persistence mechanism to provide object persistence. In particular, the persistence mechanism defines a Factory class, a Finder class, an ExpandingContainer class, a Container class and a ClassLoader class which work together to create persistent shared objects. An application can create persistent objects by calling methods on the Factory class. The Factory class then works in conjunction with an instance of the Container class and the ClassLoader class to create persistent objects in a shared address space (SAS). Shared address space is a persistent virtual address space shared by all processes running on a computer system. The SAS allows the processes to access data within SAS at any time, using a SAS address.

US Patent:

6330709, Dec 11, 2001

Filed:

Mar 30, 1998

Appl. No.:

9/050832

Inventors:

Maynard Paul Johnson - Rochester MN
Steven Jay Munroe - Rochester MN
John Gerard Nistler - Rochester MN
James W. Stopyro - Rochester MN

Assignee:

International Business Machines Corporation - Armonk NY

International Classification:

G06F 945

US Classification:

717 1

Abstract:

The preferred embodiment of the present invention facilitates the creation, storage and interaction of persistent objects using single level storage semantics on commodity systems. Specifically, the present invention defines several objects used to implement persistent objects in a shared address space. The preferred embodiment includes a Class Encapsulator class and the Object Encapsulator class that are preferably designed to encapsulate the class data and instance data, respectively. In particular, a Class Encapsulator object would preferably be created in a Persistent Container for each class of objects loaded into that Persistent Container. The Class Encapsulator object would include all of the specific data needed to implement its corresponding class. Likewise, an Object Encapsulator object would preferably be created to encapsulate each object to be stored persistently in the shared address space. A Persistent Handle class is preferably defined to store the shared address space address of the Class Encapsulator object and the Object Encapsulator object.