Method and apparatus for storing persistent objects on a distributed object network using a marshaling framework

• US 5,809,507 A
• Filed: 07/01/1996
• Issued: 09/15/1998
• Est. Priority Date: 07/01/1996
• Status: Expired due to Term

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Cavanaugh, Ken M. III
• Primary Examiner(s): Amsbury, Wayne
• Assistant Examiner(s): HOMERE, JEAN RAYMOND
• Application Number:
  US08/677,013
• Time in Patent Office: 806 Days
• Field of Search: 707/103, 707/101, 707/100, 707/10, 395/200.03, 395/200.11, 395/200.33
• US Class Current: 1/1
• CPC Class Codes: G06F 9/4493 Object persistence
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

Data structures, methods and devices for implementing persistence data storage such that persistent objects may be efficiently created and accessed in a distributed client/server computing system are disclosed. In one aspect of the invention, a method for managing persistence data for installed persistent objects involves marshaling a persistent object attribute value into a marshal buffer to provide an encoded persistent object attribute value, updating the persistent object attribute value to provide an updated persistent object attribute value, unmarshaling the updated persistent object attribute value from the marshal buffer to provide a decoded updated persistent object attribute value, and writing the decoded updated persistent object attribute value to the data store. In another aspect of the invention, a method for writing decoded updated persistent object attribute values to the data store includes extracting an index of persistent object attributes stored in the data structure, finding the location of the persistent object attribute in the data base, adding the persistent object attribute to the data store if the persistent object attribute cannot be found in the index, and writing the persistent object attribute value to the data store at the location corresponding to the persistent object attribute.

Claims

1. In a distributed object system having persistent objects installed thereon, a method for managing persistence data for the installed persistent objects, the persistence data being written to a data store, the persistence data including a persistent object attribute having a persistent object attribute value, the method comprising the steps of:

a) marshaling the persistent object attribute value into a marshal buffer, wherein marshaling the persistent object value into the marshal buffer provides an encoded persistent object attribute value;

b) updating the encoded persistent object attribute value to provide an encoded updated persistent object attribute value, wherein the encoded updated persistent object attribute value is provided in the marshal buffer;

c) unmarshaling the encoded updated persistent object attribute value from the marshal buffer to provide a decoded updated persistent object attribute value; and

d) writing the decoded updated persistent object attribute value to the data store.

2. The method of claim 1, further including the step of retrieving the persistent object attribute value from the persistent object prior to the step of marshaling the persistent object attribute value into the marshal buffer.

3. The method of claim 1, further including the step of retrieving the persistent object attribute value corresponding to the persistent object attribute from the data store prior to the step of marshaling the persistent object attribute value into the marshal buffer.

4. The method of claim 3, wherein said step of retrieving the persistent object attribute value corresponding to the persistent object attribute from the data store includes the steps of:

a) opening the data store;

b) extracting an index of persistent object attributes contained in the data store from the data store;

c) searching the index of persistent object attributes contained in the data store to determine the location of the persistent object attribute in the data store;

d) identifying the location of the persistent object attribute in the data store; and

e) returning the persistent object attribute value corresponding to the persistent object attribute.

5. The method of claim 4, wherein the step of opening the data store includes the steps of:

a) selecting an appropriate data store file associated with the data store;

b) creating the marshal buffer using the appropriate data store file;

c) creating a data store root object associated with the data store; and

d) registering the data store with a data store registry.

6. The method of claim 5, further including the steps of:

a) unmarshaling a data store version record corresponding to the data store file; and

b) determining whether the data store file is supported as the data store.

7. The method of claim 6, further including the step of unmarshaling persistence data associated with the persistent object attribute from the data store file.

8. The method of claim 1, wherein the step of writing the decoded updated persistent object attribute value to the data store comprises the steps of:

a) extracting an index of persistent object attributes stored in the data store;

b) determining whether the persistent object attribute is located in the data store using the index of persistent object attributes;

c) adding the persistent object attribute to the data store if it is determined that the persistent object attribute is not located in the index of persistent object attributes; and

d) writing the persistent object attribute value to the data store at location corresponding to the persistent object attribute when it is determined that the persistent object attribute is located in the data store.

9. In a distributed object system having persistent objects installed thereon, a method for managing persistence data for the installed persistent objects, the persistence data being written to a data store, the persistence data further including a persistent object attribute having a persistent object attribute value and a persistent object attribute name, the method comprising the steps of:

a) invoking a first method on the distributed object system, the first method being associated with the persistent object attribute having the persistent object attribute value and the persistent object attribute name;

b) marshaling the persistent object attribute value into a marshal buffer to provide thereby an encoded persistent object attribute value;

c) updating the encoded persistent object attribute value to provide an encoded updated persistent object attribute value;

d) unmarshaling the encoded updated persistent object attribute value from the marshal buffer to provide a decoded updated persistent object attribute value; and

e) writing the decoded updated persistent object attribute value to the data store.

10. The method of claim 9, further including the step of retrieving the persistent object attribute value from the persistent object prior to the step of marshaling the persistent object attribute value into the marshal buffer.

11. The method of claim 9, further including the step of retrieving the persistent object attribute value from the data store prior to the step of marshaling the persistent object attribute value into the marshal buffer.

12. The method of claim 11, wherein the step of retrieving the persistent object attribute value from the data store includes the steps of:

a) opening the data store;

b) extracting from the data store an index of persistent object attributes, the index of persistent object attributes being contained in the data store;

c) searching the index of persistent object attributes contained in the data store using the persistent object attribute name to determine a location of the persistent object attribute in the data store; and

d) returning the persistent object attribute value corresponding to the persistent object attribute.

13. The method of claim 12 wherein the step of opening the data store includes the steps of:

a) selecting an appropriate data store file;

b) creating the marshal buffer using the appropriate data store file;

c) unmarshaling a data store version record corresponding to the data store file;

d) determining whether the data store file is supported as the data store;

e) creating a data store root object associated with the data store when it is determined that the data store file is supported as the data store;

f) unmarshaling the persistence object attribute value associated with the persistent object attribute from the data store file; and

g) registering the data store with a data store registry.

14. The method of claim 9, wherein the step of writing the decoded updated persistent object attribute value to the data store includes the steps of:

a) extracting an index of persistent object attributes stored in the data store;

b) finding the location of the persistent object attribute in the data store using the persistent object attribute name and the index;

c) adding the persistent object attribute to the data store when the persistent object attribute is not found in the index;

d) and writing the persistent object attribute value to the data store at the location corresponding to the persistent object attribute when the persistent object attribute is found in the index.

15. A distributed object system arranged to store persistence data for installed persistent objects in a data store, the persistence data being written to a data store, the persistence data further including a persistent object attribute having an associated persistent object attribute value, the distributed object system comprising:

a) a processor;

b) a mass storage mechanism on which the persistence data is stored;

c) a marshaling mechanism for encoding the persistent object attribute value into a marshal buffer to provide thereby an encoded persistent object attribute value; and

d) an unmarshaling mechanism for decoding the encoded persistent object attribute value from the marshal buffer to provide a decoded persistent object attribute value.

16. The distributed object system arranged to store persistence data for installed persistent objects in a data store as recited in claim 15 further including:

a) a data store selector for selecting an appropriate data store file associated with the data store;

b) a data store creator for creating a data store root object associated with the data store; and

c) a registration mechanism for registering the data store with a data store registry.

17. The distributed object system arranged to store persistence data for installed persistent objects in a data store as recited in claim 16 further including a support mechanism for determining whether the data store file is supported as the data store.

18. The distributed object system arranged to store persistence data for installed persistent objects in a data store as recited in claim 15 further including:

a locator for finding the location of the persistent object attribute in the data store; and

an appending mechanism for adding the persistent object attribute to the data store when the persistent object attribute is not found in the data store.

19. A computer program product including a computer-usable medium having computer-readable code devices embodied thereon for implementing a persistence data storage framework, the persistence data storage framework comprising:

a) an instance of a persistent object class, the instance of the persistent object class including a set of persistent object attribute values;

b) a persistence data storage mechanism associated with the instance of the persistent object class; and

c) instances of classes which define a pluggable back-end associated with the persistence data storage mechanism.

20. A computer program product comprising a computer-usable medium having computer-readable code embodied thereon as recited in claim 19 wherein the pluggable back-end is a data store.

21. A computer program product comprising a computer-usable medium having computer-readable code embodied thereon as recited in claim 19 further comprising an instance of a method-table class associated with the instance of the persistent object class, wherein the instance of the method-table class includes methods pertaining to the set of persistent object attribute values.

22. A computer program product comprising a computer-usable medium having computer-readable code embodied thereon as recited in claim 21 wherein the methods pertaining to the set of persistent object attribute values includes at least one of a set attribute method and a get attribute method.

23. A computer program product comprising a computer-usable medium having computer-readable code embodied thereon as recited in claim 19 wherein the persistence data storage mechanism comprises instances of classes with methods associated therewith, the instances of classes and the methods being used to associate the instance of the persistent object class with the pluggable back-end.

24. A computer program product including a computer-usable medium having computer-readable code devices embodied thereon for storing state data for persistent objects in a data store defined within a distributed object system, the data store containing information corresponding to the persistent objects, the data store further containing information corresponding to attributes used to invoke methods in the distributed object system, the data store comprising:

a) a root node which identifies a version of the data store;

b) at least one persistent object associated with the root node;

c) at least one attribute associated with the persistent object, the at least one attribute including an attribute name and an attribute value;

d) an object identifier associated with the persistent object which identifies the persistent object; and

e) at least one type identifier which associates the persistent object with a corresponding method table, wherein the method table includes at least one method which is arranged to be invoked by the persistent object.

25. A computer program product as recited in claim 24 wherein the object identifier includes:

a) a database identifier which identifies the data store with which the object identifier is associated;

b) an object identifier index which identifies whether the persistent object is a valid persistent object; and

c) a subcontract identifier which identifies an associated subcontract.

26. A computer program product as recited in claim 25 wherein the database identifier includes:

a) a time stamp which identifies the time at which the data store was last modified;

b) a process identifier which identifies a process with which the data store is associated; and

c) a counter which represents the number of times the data store is opened.

27. A computer program product as recited in claim 25 wherein the object identifier index includes:

a) an index which represents a location of the persistent object within a sequence of the persistent objects associated with the data store; and

b) a counter which identifies whether the persistent object is valid.

28. A computer system for storing persistence data for a first persistent distributed object, the persistence data for the first persistent distributed object including an attribute name and an attribute value, the computer system comprising:

a) a persistent data storage mechanism arranged to process and store the persistence data for the first persistent distributed object; and

b) a representation of a data store which is configured to be adapted such that different back-end representations of the data store may be included with the persistent object storage mechanism.

29. A computer system as recited in claim 28 wherein the data store is arranged to store the attribute name and the attribute value of the persistence data for the first persistent distributed object.

30. A computer system as recited in claim 28, wherein the data store includes a plurality of objects, which objects are coupled with the first persistent distributed object through at least one inheritance relationship defining operations for exchanging an attribute value between the data store and the first persistent distributed object and for manipulating the attribute value in the data store.

31. A computer system as recited in claim 30, wherein the inheritance relationship between the data store and the first persistent distributed object comprises at least one object class defining a persistence data storage mechanism through which persistence data can be written and retrieved from the data store.

32. A computer system as recited in claim 31, wherein the first persistent distributed object is coupled with the persistence data storage mechanism through an inheritance relationship between a method table class contained in the first persistent distributed object and a method table registry class contained in the persistence data storage mechanism.

33. A computer system as recited in claim 32, wherein the inheritance relationship further includes a relationship between the persistent class that includes the attributes of the first persistent distributed object and at least one class contained in the persistent data storage mechanism that defines operations on the attribute values associated with the attributes.

34. A computer system as recited in claim 31, wherein the data store is coupled with the persistence data storage mechanism through at least one inheritance relationship which includes an inheritance relationship between a root object class contained in the data store and the persistence data storage mechanism.

35. A computer system as recited in claim 34, wherein the data store is coupled with the persistence data storage mechanism through at least one inheritance relationship which includes an inheritance relationship between a database object class contained in the data store and the persistence data storage mechanism.