×

Method for maintaining a history of system data and processes for an enterprise

  • US 5,581,755 A
  • Filed: 01/31/1995
  • Issued: 12/03/1996
  • Est. Priority Date: 01/31/1995
  • Status: Expired due to Term
First Claim
Patent Images

1. In a computer system having a user interface, a memory, an object-oriented repository, a repository program operating in said computer system executing a method responsive to a user request for maintaining an historical state of an object stored in said repository comprising the steps of:

  • a. if a new logical object is requested, constructing a new versioned object;

    b. if a new logical object is not requested, retrieving from said repository an existing object on which a new state is to be based;

    c. if said new state is derived from two objects, retrieving from said repository the other object on which said new state is to be based;

    d. deriving a new object from said existing object if said new object state is not derived from two objects, and if said new object state is derived from two objects, deriving a new object by merging said existing object and said other object by;

    i) validating merge request by insuring that neither said existing object nor said other object are in a ghost state, the two objects to be merged are not the same object, the two objects are members of same version graph and merge will not cause two objects from the same variant branch to be merged into a new object also on the same variant branch;

    ii) reserving said existing object if said validating step indicates that the merge request is valid; and

    ,iii) if said reserve operation was successful, adding said other object which was merged with said existing object to a list of previous versions of said new object and return derived said new object to caller;

    e. receiving any necessary changes to state of said new object;

    f. unreserving said new object if said changes are not to be retained, and if said changes are to be retained, replacing said new object by;

    i) validating replace request by insuring that said new object is in a ghost state and said new object is in the context of the requestor; and

    ,ii) setting reserve status of said new object to available if said validating step indicates that said replace request is valid;

    g. continuously repeating all steps hereof for each user request.

View all claims
  • 9 Assignments
Timeline View
Assignment View
    ×
    ×