Browse Prior Art Database

Object Creation Mechanism for an Object Management System

IP.com Disclosure Number: IPCOM000084212D
Original Publication Date: 1975-Oct-01
Included in the Prior Art Database: 2005-Mar-02
Document File: 3 page(s) / 50K

Publishing Venue

IBM

Related People

Bennett, RB: AUTHOR [+2]

Abstract

An object creation mechanism is described wherein new operating And programming system functions or "objects" are created by service requests to existing objects. This makes possible an object based protection and authority scheme that is consistent for object creation, as well as object access. It also provides consistent control points for objects of the same classification.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 49% of the total text.

Page 1 of 3

Object Creation Mechanism for an Object Management System

An object creation mechanism is described wherein new operating And programming system functions or "objects" are created by service requests to existing objects. This makes possible an object based protection and authority scheme that is consistent for object creation, as well as object access. It also provides consistent control points for objects of the same classification.

The basic object management system is described in an article entitled "Object Management System" by R.B. Bennett appearing in the IBM Technical Disclosure Bulletin, Vol. 18, No. 5, October 1975, pages 1356-1360. As there indicated, each operating or programming system function is structured as an "object" and each such object is formed from the combination of two primitive or basic elements, one of which is called a data space (DS) and the other of which is called a service function set (SFS). The basic structure for a single object or function is shown in Fig. 1.

The data space D1 is the space where data for the object is stored. The service function set is used to define groups of executable statements for the object. It includes a set of named functions (e.g., F1-1 through F1-4) consisting of one for each service request that is supported for the object. The object's contents are accessible to a user only through service requests, which include the identification (ID) of the object and the name of the particular service function (e.g., F1-3) to be invoked.

In the above-referenced article, the creation of new objects is treated as a special case in that the DS and SFS elements for each new object are user defined and built to provide the particular functions specified by the user. The present proposal, on the other hand, provides an improved object creation mechanism, whereby the creation of a new object takes the form of a service request to an existing object which provides a model for the new object. This represents a more consistent approach whereby: (a) All objects have the potential for object procreation. Objects may be created from other objects, using a service function of the originating object. In this way, object creation conforms to the same authority scheme as normal object access. (b) The object creator need not supply the service function set (SFS) and data space (DS) formats and values upon each creation. (c) Multiple levels of object creation form an origin tree that permits evolution of function in a system. (d) Optionally, an originating object may maintain control over those objects that are created from it.

Objects may have the property of being object originating, determined by the existence of a create-type service function in the associated SFS. Object 2 in Fig. 2 has this property. An object is always created through another object which acts as the originator for the new object. All objects created from the same originating object are of the same type, i.e., they inherit...