Importance

Loading Importance Indicators...

Abstract

An 'Object Cycle' versioning system having an Object Cycle Server is described. The server communicates over a wire or a network for providing versioning services to multiple clients. During a user session, a user invokes operation of the system from within the development environment of the particular client being used. From the perspective of the Object Cycle Server, each client is simply 'a client' (without regard to proprietary nature) which desires to store 'an object.' The Object Cycle Server, in turn, maps the object into a meta model which serves as a container for facilitating version control. With the model, therefore, operations supported by the system for versioning will execute correctly even if the objects are stored in a format other than a relational database, such as an object-oriented database, a file server, or other storage system. The model separates out the name of an object from where the object itself is actually stored. As additional versions of the object are created, the number of object instances increases. Once an instance has been created, versioning activities can be undertaken, such as checking in, checking out, and the like--operations which are atomic at the object level. By separating out these areas of functionality into (conceptually) different nodes of a meta model, system performance is enhanced.

Loading the Abstract Image...

First Claim