GB2266172A - Object-oriented data management system - Google Patents
Object-oriented data management system Download PDFInfo
- Publication number
- GB2266172A GB2266172A GB9304312A GB9304312A GB2266172A GB 2266172 A GB2266172 A GB 2266172A GB 9304312 A GB9304312 A GB 9304312A GB 9304312 A GB9304312 A GB 9304312A GB 2266172 A GB2266172 A GB 2266172A
- Authority
- GB
- United Kingdom
- Prior art keywords
- class
- services
- objects
- managed
- attributes
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
- G06F9/4493—Object persistence
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
A data processing system is described, which enables the creation of managed objects 20, each managed object inheriting attributes and services of a managed object class. The system also enables the creation of object managers 22, each object manager inheriting attributes and services of an object manager class. Each object manager is arranged to manage storage and retrieval of a predetermined group of the managed objects. Short-term (transient and cache) objects 26, 28 are stored in main memory, whereas persistent objects 24 are stored in magnetic or optical disc units. <IMAGE>
Description
DATA MANAGEMENT MECHANISM
Background to the Invention
This invention relates to a mechanism for data management within a data processing system.
More specifically, the invention is concerned with systems implemented using object-oriented design (OOD) techniques.
For details of object oriented design reference is made to "Object-Oriented Analysis", P Coad & E Yourdan, Prentice Hall (1991), and "Object-Oriented Design", P Coad & E Yourdan,
Prentice Hall, (1991).
Conventional design methods are based on the use of functional decomposition, where large problems are broken into smaller ones by concentrating on dividing the major steps which appear in the flow of control. The main limitation of designs produced by such methods is that they are not particularly good at coping with change, which often accounts for the majority of a data processing system's life.
The main distinction between Object-Oriented Design and conventional design is that it is object-oriented and not process-oriented.
Central to OOD is the concept of an 'object'. An object embodies an abstraction of information which is meaningful to its clients. It has the following properties: a) An object has attributes specifying all the (usually static) properties and the current (usually dynamic) values of each of these properties.
b) An object has behaviour defined by the 'services' it provides to its clients (other objects or programs). The terms 'operator' or 'method' are sometimes used instead of 'service'. Clients do not generally directly access the data in an object; they send 'messages' to the object requesting services to be carried out to access or manipulate the actual data in the object. The term 'request' is sometimes used instead of 'message'. A service may be classified as:
Modifier - alters the state of an object;
Selector - accesses the state of an object without
modifying it;
Iterator - permits the parts of an object to be
visited;
Constructor - creates an object initialising its state;
Destructor - destroys the object freeing its state.
In this way, objects provide information-hiding by data encapsulation. By avoiding direct client access to the data, a system can guarantee certain integrity constraints of the object. It is also possible to change the object implementation without affecting the clients, unless there is a change in the nature of the services provided.
c) An object has identity and is denoted by a name. To make a request, a client identifies the object which is to perform the service and names the request. Requests may take arguments (including references to other objects) and the service may return one or more results.
d) An object is an instance of some class. A class contains a common structure and a common behaviour applicable to all instances of the class. Classes can be derived from other classes (inheritance).
In such a system, it is necessary to provide some means for managing the storage and retrieval of objects, which may be held in different kinds of storage medium such as, for example, magnetic discs, optical discs or semiconductor memory.
The object of the present invention is to provide an improved data management mechanism for managing the storage and retrieval of objects.
Summary of the Invention
According to the present invention there is provided a data processing system comprising: a) a managed object class, comprising a plurality of
attributes and services, b) means for creating a plurality of managed objects, each
managed object inheriting attributes and services of the
managed object class, c) an object manager class, comprising a plurality of
attributes and services, and d) means for creating plurality of object managers, each
object manager inheriting attributes and services of the
object manager class, each object manager being arranged
to manage storage and retrieval of a predetermined group
of said managed objects.
Brief Description of the Drawings
Figure 1 is a block diagram of a data processing system embodying the invention.
Figure 2 is a schematic diagram showing a number of object managers and managed objects.
Figure 3 is a schematic diagram showing a number of classes from which objects can be derived.
Figure 4 is a flow diagram illustrating a REGISTER service provided by an object manager.
Figure 5 is a flow diagram illustrating a GETCURRENT service provided by an object manager.
Description of an Embodiment of the Invention
One data processing system embodying the invention will now be described by way of example with reference to the accompanying drawings.
Referring to Figure 1, the system comprises a central processing unit 10 having a main memory 12, and one or more long-term memory units 14 such as magnetic disc units or optical disc units. As will be described, the main memory 12 is used for short-term (transient and cache) storage, while the long-term storage units 14 are used to provide a persistent storage facility.
Referring to Figure 2, the system contains a number of objects 20, referred to as managed objects. The exact nature of these objects forms no part of the present invention and so need not be described in detail. For example, in a cryptographic services system, the managed objects may include cryptographic context objects, algorithm objects and event objects.
The system also provides a number of objects referred to as object managers 22. As will be described in detail later each object manager provides services for managing the storage and retrieval of the managed objects 20. Each object manager 22 is specialised in managing a particular class of object or group of classes. For example, one object manager may be specialised for managing cryptographic context objects.
Each object manager 22 may have one or more persistent store objects 24 associated with it. Each persistent store object encapsulates an area of long-term storage (eg disc) and provides services to the object manager to allow storage and retrieval of managed objects from that area.
Each object manager 22 may also have one or more transient store objects 26 associated with it. Each transient store object 26 encapsulates an area of short-term storage (ie main memory) and provides services to the object manager to allow storage or retrieval of managed objects from that area.
Each object manager 22 may also have a cache object 28 associated with it. Each cache object 28 encapsulates an area of short-term storage which is used as a cache for storing temporary copies of objects resident in the long-term storage.
Each object manager 22 may also have an index object 30 associated with it. Each index object contains a list of objects held in transient or persistent store, and provides services to allow reference to and updating of this list.
Referring now to Figure 3, the system contains a number of class objects (hereinafter referred to simply as classes) from which all the objects referred to above can be created as instances of the classes, or as instances of derived classes. An object created as an instance of a class will inherit the attributes and services of the class.
In the Figure, each class is represented schematically as a rectangle divided into three areas. The upper area contains the name of the class; the middle area contains the names of the attributes of the class; and the lower area contains the names of the services provided by the class.
Each of the classes will now be described in turn.
Managedobject This class contains attributes and services required by all the managed objects 20. The class may be specialised, by means of derived classes, tailored to particular types of managed object. All the managed objects 20 are created as instances of these derived classes.
The ManagedObject class contains the flowing attributes:
Version: the version number of the system on which the managed object was created.
Persistent: this indicates whether the managed object should be stored in long-term storage.
Reference: a positive integer which uniquely identifies the managed object to its associated object manager. The value is usually generated by the object manager, but alternatively may be supplied to the object manager in which case the object manager will validate it before using it to set the
Reference attribute. This attribute may be set only by the associated object manager.
Restored: this indicates that the managed object has been restored from persistent storage.
Registered: this indicates that the managed object is registered with the appropriate object manager.
ManagerRef: this identifies the object manager which is responsible for managing the object.
Type: the type of managed object.
The ManagedObject class contains the following services:
Create: This creates a new managed object as an instance of the ManagedObject class and returns its object identifier (OID). Optionally, it may also call the Register service of the appropriate object manager (see below) to register the object with that object manager.
Release: This releases all resources associated with the managed object and if necessary, calls the Deregister service of the appropriate object manager to deregister the object.
Store: This causes the managed object to create an image of itself, in the form type, length, value, suitable for storing in long-term storage.
Restore: This accepts a storable image (in the form type, length, value) and creates an object from this image, returning its OID. The Restored attribute of the created object is set.
Set: This sets the value of any attribute in the object, except Restored, to a specified value.
Get: This gets the value of any attribute in the managed object.
ObjectManager
This class contains attributes and services required by all the object managers 22. This class may be specialised by means of derived classes, so as to tailor the attributes and services to a particular kind of managed object. All the object managers are derived as instances of these derived classes.
The ObjectManager class contains the following attributes.
FilterType: This attribute is used by the Locate service of the object manager to specify a particular type of managed object to be located.
FilterRef: This is used by the Locate service to specify a particular managed object reference which is to be located.
The ObjectManager class contains the following services.
Register: this allows managed objects to register themselves with an object manager, or to be registered by other objects.
A flow diagram of the Register service is shown in Figure 4.
The Register service first checks the Restored attribute of the object being registered. If this is set, the Add service of the cache object is called to add the object being registered to the cache. A call is made to the Add service of the associated index object to update the index object by adding the object being registered. The Registered attribute of the object being registered is then set, and finally the
ManagerRef attribute of the registering object is set, before returning.
If the Restored attribute is not set, the Register service checks whether a Reference value has been supplied in the call to the Register service and, if so, validates it. If the supplied Reference value is invalid, the service returns, indicating failure. If a Reference value has not been supplied, a Reference value is generated. The generated or validated Reference value is then set in the object being registered.
The Register service then checks whether the Persistent attribute is set in the object being registered.
If Persistent is set, the Register service must make a persistent copy of the object as follows. First, a call is made to the Store service of the object being requested to create an image of the object. The image is then modified to include the OID of the object and the image is appended to the persistent file by means of a call to the appropriate persistent store object. The object is then added to the cache, the index is updated and the Registered and ManagerRef attributes are set as described above.
If Persistent is not set, then the object being registered is held only in transient store. In this case, the Register service checks whether a transient store object already exists for this object manager. If not, a call is made to the Create service of the TransientStore class to create a new transient store object associated with this object manager. A call is then made to the Add service of the transient store object, to add the object being registered to this transient store. The index is then updated and the
Registered and ManagerRef attributes are set as described above.
Deregister: this service allows previously registered objects to deregister themselves, or to be deregistered by other objects. This provides a way of indicating to an object manager that a managed object no longer exists in memory (ie the object is being or has been deleted).
The Deregister service does not attempt to release the resources held by the manage object: this is done by other services. Moreover, the Deregister service does not delete an object from persistent store: this is done by the Delete service (see below).
Reset: this calls the Reset service of the associated index object, to reset the CurrentRef attribute of the index object. It also resets the FilterRef and FilterType attributes of the object manager to null values.
GetCurrent: this service allows a current object to be accessed. A flow diagram of this service is shown in
Figure 5.
The GetCurrent service first calls the GetCurrent service of the associated index object. If this is not successful a failure is indicated.
If the call is successful the index will return either the OID of the current object (if the object is in the main memory) or an offset value, if the object is only in long-term storage.
If an offset value was returned, the GetCurrent service must restore the object to the main memory as follows. First, calls are made to the Goto and Read services of the associated persistent store object to access and return a representation of the required object from the long-term storage device. A call is then made to the Restore service of the object to restore the object. A call is then made to the Register service of the object manager, to register the restored object.
Finally, a call is made to the Locate service of the index object, passing it the values of the FilterRef and FilterType attributes of the object manager (if set). The index object will then locate the next object, if any, whose attributes match these filters. The Reference value of the located object is placed in the CurrentRef attribute, ready for the next GetCurrent call.
Locate: If a reference or type value is specified, this service sets the FilterRef and/or Filter Type attributes to the specified values; otherwise it leaves these attributes unchanged. It then calls the Locate service of the associated index object, passing it the values of FilterRef and FilterType as parameters.
Delete: This removes a specified managed object from the persistent or transient store.
If the object exists in memory, the Delete service calls the
Release service of the object, to get it to release all its resources and to deregister itself.
If there is a cache object associated with the object manager, the Delete service calls the Remove service of this cache object, to remove the managed object from the cache.
If there is an index object associated with the object manager, the Delete service calls the Remove service of this index object to remove the managed object from the index.
Create: This creates a new object manager as an instance of the ObjectManager class and returns the OID of the created object manager.
Release: This releases all resources associated with a specified object manager. If there are any persistent store objects associated with this object manager, the Release service of each of these persistent store objects is called to release it. Similarly, if there are any associated transient store objects, the Release service of each of them is called.
PersistentStore
This class contains attributes and services required by the persistent store objects 24. All the persistent store objects are derived as instances of this class.
This class may be specialised by means of derived classes to cater for different forms of long-term storage such as optical disc, magnetic tape, access-controlled memory, or on-board key storage in a cryptographic chip.
The PersistentStore class contains the following attributes:' FileName: the name of the persistent file.
Path: the path to the persistent file.
CurrentOffset: a pointer to the current position in the persistent file.
The PersistentStore class contains the following services:
Read: read and return the current record from the long-term storage medium.
Append: append a supplied record to the end of the long-term storage medium.
Delete: delete the record at the position specified by CurrentOffset.
Create: this creates a new persistent store object as an instance of the PersistentStore class, and returns its OID.
It also optionally creates a new cache object associated with the persistent store object.
Release: this releases the resources associated with specified persistent store object. Also, if there exists an associated cache object it calls the Release of that cache object to release the services associated with it.
TransientStore
This class contains attributes and services required by the transient store objects 26. All the transient store objects are created as instances of this class.
The TransientStore class contains the following attributes:
MaxEntries: this attribute is set when a transient store object is created and indicates maximum number of entries allowed in the ObjectList.
ObjectList: a list of OIDs of objects held in the transient store.
The TransientStore class contains the following services:
Add: this service adds an OID to the ObjectList, provided that adding the entry does not cause the number of items in the list to exceed the value specified by the MaxEntries attribute. If MaxEntries would be exceeded the entry is not added and the service returns indicating failure.
Remove: this calls the Release service of a specified object and removes the OID of that object from the ObjectList.
Create: this creates a new transient store object as an instance of the TransientStore class and returns its OlD.
Release: this calls the Release services of all objects specified by the ObjectList. It then releases the resources associated with the transient store object.
Set: Sets the value of MaxEntries.
Get: Gets the value of MaxEntries.
Cache
This class contains attributes and services required by the cache objects 28. All the cache objects are created as instances of this class.
The cache class contains attributes MaxEntries and
ObjectLists similar to those for the TransientStore class.
The cache class contains the following services:
Add: this adds an OID to the ObjectList. If adding an entry causes the number of items in the list to exceed MaxEntries, then one existing entry is removed from the ObjectList and its associated resources are released to make room for the new entry. This service then calls the Amend service of the associated index object to update it.
Remove: removes a specified entry from the ObjectList.
Create: creates a new cache object as an instance of the
Cache class and returns its OlD.
Release: calls the Release services of all the objects on the
ObjectList and then releases the resources associated with the cache object.
Set and Get: similar to those for the TransientStore class.
Index
This class contains attributes and services required by all the index objects 30. All the index objects are created as instances of this class.
The Index class contains the following attributes:
ObjectList: a list of objects held in transient or persistent store. For each such object the list holds an entry containing the following items:
- object type
- object reference
- object identifier (OID) - the offset from the start of the store to the start
of the object (eg a file offset).
Optionally, further search criteria may also be held.
CurrentRef: the reference of a current managed object. This attribute can be changed only by using the Locate or Reset services described below.
The Index class contains the following services:
Add: adds a specified entry to the ObjectList.
Remove: removes a specified entry from the ObjectList.
Amend: amends the object identifier in a specified entry of the ObjectList to a specified value. This service is normally used when an existing object is added to or removed from cache.
Reset: sets the value of CurrentRef to that of the first object (ie the object with the lowest reference number). If no objects exist, this value will be zero.
GetCurrent: returns an identifier of the object whose reference is held in the CurrentRef attribute. If this object is in cache or transient store, the identifier is the OID of the object. If the object is in persistent store but not in cache or transient store, the identifier is the offset of the object.
Locate: searches for objects that match a specified search criteria, starting from CurrentRef. If a matching object is found, CurrentRef is set to refer to this object. If, on the other hand, no matching object is found, CurrentRef is set to zero.
Create: creates a new index object as an instance of the
Index class and returns its OID.
Release: releases the resources associated with the index object.
Claims (6)
1. A data processing system comprising:
a) a managed object class, comprising a plurality of
attributes and services,
b) means for creating a plurality of managed objects
each managed object inheriting attributes and
services of the managed object class,
c) an object manager class, comprising a plurality of
attributes and services, and
d) means for creating a plurality of object managers,
each object manager inheriting attributes and
services of the object manager class, each object
manager being arranged to manage storage and
retrieval of a predetermined group of said managed
objects.
2. A system according to Claim 1 further including
a) a persistent store class, comprising a plurality of
attributes and services and
b) means for creating persistent store objects
associated with the object managers, each
persistent store object inheriting attributes and
services of the persistent store class and being
arranged to encapsulate an area of long-term
storage.
3. A method of operating a data processing system
comprising the steps:
a) providing a managed object class, comprising a
plurality of attributes and services,
b) creating a plurality of managed objects each
managed object inheriting attributes and services
of the managed object class,
c) providing an object manager class, comprising a
plurality of attributes and services, and
d) creating a plurality of object managers, each
object manager inheriting attributes and services
of the object manager class, each object manager
being arranged to manage storage and retrieval of a
predetermined group of said managed objects.
4. A method according to Claim 3 further comprising the
steps of:
a) providing a persistent store class, comprising a
plurality of attributes and services and
b) creating persistent store objects associated with
the object managers, each persistent store object
inheriting attributes and services of the
persistent store class and being arranged to
encapsulate an area of long-term storage.
5. A data processing system substantially as hereinbefore
described with reference to the accompanying drawings.
6. A method of operating a data processing system
substantially as hereinbefore described with reference
to the accompanying drawings.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| GB929208275A GB9208275D0 (en) | 1992-04-15 | 1992-04-15 | Data management mechanism |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| GB9304312D0 GB9304312D0 (en) | 1993-04-21 |
| GB2266172A true GB2266172A (en) | 1993-10-20 |
Family
ID=10714067
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| GB929208275A Pending GB9208275D0 (en) | 1992-04-15 | 1992-04-15 | Data management mechanism |
| GB9304312A Withdrawn GB2266172A (en) | 1992-04-15 | 1993-03-03 | Object-oriented data management system |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| GB929208275A Pending GB9208275D0 (en) | 1992-04-15 | 1992-04-15 | Data management mechanism |
Country Status (1)
| Country | Link |
|---|---|
| GB (2) | GB9208275D0 (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO1995016957A1 (en) * | 1993-12-17 | 1995-06-22 | Taligent, Inc. | Object-oriented memory allocation framework |
| WO1995016960A1 (en) * | 1993-12-17 | 1995-06-22 | Taligent, Inc. | Rendering cache in an object oriented system |
| EP0701201A1 (en) * | 1994-08-31 | 1996-03-13 | Siemens Aktiengesellschaft | Dynamic object management method for a device which is programmed in an object orientated manner |
| GB2308209A (en) * | 1995-12-14 | 1997-06-18 | Ibm | An object-oriented information handling system |
| EP0871117A1 (en) * | 1996-10-31 | 1998-10-14 | Sony Corporation | Information processing system and information processing method |
| EP0955577A1 (en) | 1998-05-04 | 1999-11-10 | International Business Machines Corporation | Method and device for creating an object in a non-persistent memory and/or keeping accessibility to said object |
| WO2000077613A2 (en) * | 1999-06-14 | 2000-12-21 | Wind River International Inc. | Method and system for managing and using persistent storage |
| US6490616B1 (en) | 1999-06-14 | 2002-12-03 | Wind River International, Ltd. | Method and apparatus for incremental download from server to client |
| US6857015B1 (en) | 1999-06-14 | 2005-02-15 | Wind River International, Ltd. | Method and system for remotely observing and controlling objects |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0304071A2 (en) * | 1987-08-21 | 1989-02-22 | Wang Laboratories Inc. | Data integration by object management |
| WO1991011766A2 (en) * | 1990-01-30 | 1991-08-08 | Johnson Service Company | Networked facilities management system |
| EP0501610A2 (en) * | 1991-02-25 | 1992-09-02 | Hewlett-Packard Company | Object oriented distributed computing system |
-
1992
- 1992-04-15 GB GB929208275A patent/GB9208275D0/en active Pending
-
1993
- 1993-03-03 GB GB9304312A patent/GB2266172A/en not_active Withdrawn
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0304071A2 (en) * | 1987-08-21 | 1989-02-22 | Wang Laboratories Inc. | Data integration by object management |
| WO1991011766A2 (en) * | 1990-01-30 | 1991-08-08 | Johnson Service Company | Networked facilities management system |
| EP0501610A2 (en) * | 1991-02-25 | 1992-09-02 | Hewlett-Packard Company | Object oriented distributed computing system |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO1995016960A1 (en) * | 1993-12-17 | 1995-06-22 | Taligent, Inc. | Rendering cache in an object oriented system |
| US5530799A (en) * | 1993-12-17 | 1996-06-25 | Taligent Inc. | Rendering cache in an object oriented system |
| WO1995016957A1 (en) * | 1993-12-17 | 1995-06-22 | Taligent, Inc. | Object-oriented memory allocation framework |
| US6173336B1 (en) | 1994-08-31 | 2001-01-09 | Siemens Aktiengesellschaft | Method for the administration of dynamic objects in a means programmed object-oriented |
| EP0701201A1 (en) * | 1994-08-31 | 1996-03-13 | Siemens Aktiengesellschaft | Dynamic object management method for a device which is programmed in an object orientated manner |
| GB2308209A (en) * | 1995-12-14 | 1997-06-18 | Ibm | An object-oriented information handling system |
| GB2308209B (en) * | 1995-12-14 | 2000-06-28 | Ibm | Information handling system |
| EP0871117A1 (en) * | 1996-10-31 | 1998-10-14 | Sony Corporation | Information processing system and information processing method |
| EP0871117A4 (en) * | 1996-10-31 | 2000-02-23 | Sony Corp | Information processing system and information processing method |
| EP0955577A1 (en) | 1998-05-04 | 1999-11-10 | International Business Machines Corporation | Method and device for creating an object in a non-persistent memory and/or keeping accessibility to said object |
| EP0955577B1 (en) * | 1998-05-04 | 2011-11-30 | International Business Machines Corporation | Method and device for creating an object in a non-persistent memory and/or keeping accessibility to said object |
| WO2000077613A2 (en) * | 1999-06-14 | 2000-12-21 | Wind River International Inc. | Method and system for managing and using persistent storage |
| WO2000077613A3 (en) * | 1999-06-14 | 2001-07-05 | Wind River Internat Inc | Method and system for managing and using persistent storage |
| US6490616B1 (en) | 1999-06-14 | 2002-12-03 | Wind River International, Ltd. | Method and apparatus for incremental download from server to client |
| US6857015B1 (en) | 1999-06-14 | 2005-02-15 | Wind River International, Ltd. | Method and system for remotely observing and controlling objects |
Also Published As
| Publication number | Publication date |
|---|---|
| GB9304312D0 (en) | 1993-04-21 |
| GB9208275D0 (en) | 1992-06-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10803197B1 (en) | Masking sensitive information in records of filtered accesses to unstructured data | |
| US7526479B2 (en) | Configuration manager in enterprise computing system | |
| EP0398494B1 (en) | Maintenance of file attributes in a distributed data processing system | |
| US6061692A (en) | System and method for administering a meta database as an integral component of an information server | |
| US6915510B1 (en) | System and method for automatically modifying database access methods to insert database object handling instructions | |
| US7167874B2 (en) | System and method for command line administration of project spaces using XML objects | |
| US6055527A (en) | System, method and computer program product for superimposing attributes on hierarchically organized file systems | |
| US5588147A (en) | Replication facility | |
| CA2504322C (en) | Apparatus and method for hardware-based file system | |
| US6823338B1 (en) | Method, mechanism and computer program product for processing sparse hierarchical ACL data in a relational database | |
| US6209101B1 (en) | Adaptive security system having a hierarchy of security servers | |
| EP0797798B1 (en) | Method and apparatus to update or change a network directory | |
| US7533157B2 (en) | Method for delegation of administrative operations in user enrollment tasks | |
| WO1996041283A9 (en) | System and method for superimposing attributes on hierarchically organized file systems | |
| US20020069280A1 (en) | Method and system for scalable, high performance hierarchical storage management | |
| JP4171537B2 (en) | How to access database information | |
| JP4205179B2 (en) | Document management system | |
| US6988280B2 (en) | System and method for enhancing authorization request in a computing device | |
| GB2266172A (en) | Object-oriented data management system | |
| JPH0785020A (en) | Document managing method | |
| JP3290801B2 (en) | Resource location detection method | |
| US6816869B2 (en) | Mapping database users to operating system users in a computer schema | |
| JPH0668010A (en) | Distributed cache management system | |
| KR101091071B1 (en) | Method system and software for journaling system objects | |
| Henskens et al. | Coarse and fine grain objects in a distributed persistent store |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| WAP | Application withdrawn, taken to be withdrawn or refused ** after publication under section 16(1) |