JPH09185517A - Object management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To operate an object operating by means of sharing a memory space with the user of the object of an application and the like even in an independent memory space SOLUTION: In a class-B, the operation memory space of the object is independently set with a memory space attribute table 10. The instance 135 of a Proxy class-C corresponding to the class-B is generated at the time of generation and a new memory space 200 is generated so as to operate a stub S. An instance 225 corresponding to the class-B is operated in the memory space 200.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method of managing objects on a computer.

[0002]

2. Description of the Related Art In a distributed object management system, an object provider hides the internal structure of the object provider and discloses the functions of the object provider as procedures. Each object is distinguished by attaching an instance identifier. When using the function provided by the object provider, the object user requests the execution of the function by specifying the instance identifier and procedure. As such a distributed object management system, "X / Open Preliminar
y Specification, The Commo
n ObjectRequest Broker: Ar
chapter and Specificat
There is a system described in "ion".

In addition, when the operating system has a plurality of memory spaces as a unit of protection, an independent memory space object for operating the object provider in a memory space different from that of the object user is possible. A shared memory space object is available if the operating system has a dynamic link library, which is the facility to read programs from storage into memory space during execution. "Kraig Block
by Schmidt, Inside OLE2, Micr
In the system described in "soft PRESS", there are independent memory space objects and shared memory space objects.

[0004]

In the conventional object management, the shared memory space object cannot be executed as an independent memory space object.

Therefore, when a failure occurs in the processing of the shared memory space object, the entire memory space including the object is lost and even the data of the object user is lost.

[0006]

In order to achieve the above object, the file control method of the present invention is (1) a procedure in a memory space cannot access a procedure or data in another memory space. A class that is a program for executing a procedure for an instance on a computer that has a plurality of memory spaces and that can communicate with procedures in other memory spaces by messages and can read the program from the storage device. In the object management system of an object consisting of an instance with a reference to the class and data, register whether the memory space of the instance generation request source program and the object is shared or independent for each class in the memory space attribute of the class,
Providing a proxy class corresponding to each class, providing a stub that is a program corresponding to each proxy class,
When a class instantiation is requested and the memory space attributes of the class are independent, a proxy instance that is an instance of the proxy class corresponding to the class is created, and the proxy instance creates a new memory space and creates a stub memory. As a space, a stub corresponding to the class is loaded into the stub memory space and executed, the proxy instance requests the stub to instantiate the class, and the proxy instance uses the memory space identifier of the stub memory space and the The instance identifier of the instance is stored and the instance identifier of the proxy instance is returned. When the proxy instance is requested to execute a procedure, the instance indicated by the instance identifier stored in the proxy instance is stored. The proxy instance is requested to delete, by sending a message to the stub in the memory space indicated by the memory space identifier stored by the proxy instance to receive a response message and returning the result, and executing the procedure. When a message is sent to the stub of the memory space indicated by the memory space identifier stored by the proxy instance and a response message is received so that the instance indicated by the instance identifier stored by the proxy instance is deleted. When a result is returned, the stub ends, the stub memory space disappears, and when a failure occurs in the stub memory space, the proxy instance generation request source program continues processing.

According to the present invention, in the object management system, the shared memory space object can be operated as an independent memory space object by registering the memory space attribute. As a result, even if the failure of the object provider occurs, the range of the failure is limited to the memory space and the data of the object user is protected.

[0008]

BEST MODE FOR CARRYING OUT THE INVENTION The operation of the object management system of this embodiment according to the present invention will be described in more detail below.

FIG. 1 is a block diagram showing an embodiment of an object management system to which the present invention is applied.
And a storage device 2 is shown.
Calculator 1 is operating system 3, memory space 1
The memory space 100 includes an application 110, an object 120, and an object 130.
The memory space 200 has a stub 210 and an object 220. The storage device 2 includes a memory space attribute table 10, a stub table 20, and a stub-S file 3.
3. Has class files 30, 31, 32.

Application 110 has variables 111, 112 for storing a reference to the instance. References to instances are pointers, instance identifiers, etc.

An object consists of one class and multiple instances. In the example, the object 120,
220 and 130 are classes 121, 221, and 13 respectively
1 and instances 125, 225, 135.

A class has an instance number field for holding the number of instances of the class and a procedure. In the embodiment, the classes 121, 221, and 131 have the number of instances 122, 222, and 132 and the procedures 123 and 22, respectively.
3 and 133.

An instance has a class pointer and data that is a reference to the class. A reference to a class may be a class identifier or the like instead of a pointer. In the example, instances 125, 225, 135 have class pointers 126, 226, 136, respectively, and instance 12
5, 225 and 135 are instance data 12 respectively
7, 227, 137.

The class 131 is a proxy class. The data of an instance of the proxy class consists of a memory space identifier field and an instance identifier field. In the embodiment, it has a memory space identifier 138 and an instance identifier 139.

The memory space attribute table 10 has a class field 11 and a memory space attribute field 12. The class field 11 stores a class identifier. The memory space attribute field 12 stores whether the object has a relationship between the object user and the memory space, which is shared or independent.

The stub table 20 has a class field 2
1, a proxy class field 22 and a stub field 23. The class field 21 stores a class identifier. The proxy class field 22 stores the class identifier of the proxy class. The stub field 23 stores a reference to the stub file.

The class files 30, 31, 32 store the procedure programs of the classes 121, 221, 131, respectively.

The stub-S file 33 stores the program of the stub 210.

In FIG. 1, the entry 13 indicates class-A.
Indicates that the memory space attribute is shared, and entry 14 indicates that class-B has independent memory space attributes.

Further, it is shown that the proxy class corresponding to the classes 121 and 221 is class-C and the stub is stub-S.

FIG. 2 shows the classes 121, 221, and 13 of FIG.
3 is a block diagram showing an example of a structure of a procedure possessed by 1. The instance generation procedure 500 and the instance deletion procedure 510 process generation and deletion of an instance. Other procedures 520 and 530 perform processing for the instance.

FIG. 3 is a flow chart showing the operation of creating an instance of an application.

A class identifier is specified to request the operating system to generate an instance (1300).

The reference to the created instance is stored in a variable (1310).

FIG. 4 is a flow chart showing an instance generation operation of the operating system.

A class identifier is received (1400).

The memory space attribute table is searched to obtain the memory space attribute from the entry that matches the class identifier (1410).

The memory space attributes are examined (1420).

When the memory space attributes are independent, the stub table is searched to obtain the proxy class identifier from the entry matching the class identifier (1430), and the proxy class corresponding to the proxy class identifier is obtained (143).
1) Pass a class identifier to the proxy class instance creation procedure to request instance creation (143)
2).

When the memory space attribute is shared, the class corresponding to the class identifier is acquired (1441), and the instance creation procedure of the class is requested to create an instance (1442).

The instance identifier of the created instance is returned (1450).

FIG. 5 is a flowchart showing the class instance generation operation.

A memory area for the instance is secured in the memory space (1500).

The class pointer of the instance is set to point to the class (1510).

Initialize the data of the instance (15
20).

The instance identifier of the instance is returned (1530).

FIG. 6 is a flow chart showing the operation of creating an instance of the proxy class.

The class identifier is received (1600).

A memory area for the proxy instance is secured in the memory space (1601).

The class pointer of the proxy instance is set to point to the proxy class (1602).

The stub table is searched to obtain the stub from the entry that matches the class identifier (1603).

The operating system is requested to create a new stub memory space and load and execute the stub (1604).

The memory space identifier of the generated stub memory space is stored in the memory space identifier field of the proxy instance (1605).

A message for designating an instance by designating a class identifier is sent to the stub (160
6).

Receive a response message from the stub (1
607).

The instance identifier obtained from the response message is stored in the instance identifier field of the proxy instance (1608).

The instance identifier of the proxy instance is returned (1609).

FIG. 7 is a flow chart showing the procedure execution operation for an application instance.

Specify the procedure name and the input parameters to request the instance referenced by the variable to execute the procedure (17
00).

FIG. 8 is a flow chart showing the procedure execution operation for an instance of a class.

Receive procedure name and input parameters (1
800).

The class indicated by the class pointer of the instance is searched and the procedure matching the procedure name is executed (1
810).

The execution result is returned (1820).

FIG. 9 is a flowchart showing the procedure execution operation for an instance of the proxy class.

Receive procedure name and input parameters (1
900).

A message for designating the procedure execution by designating the instance identifier stored in the instance identifier field of the proxy instance, the procedure name, and the input parameter is stored in the memory space identifier field of the proxy instance. It transmits to the stub of the memory space shown (1910).

Receive a response message from the stub (1
920).

The execution result is returned (1930).

FIG. 10 is a flow chart showing the operation of deleting an instance of an application.

The instance referred to by the variable is requested to execute the instance deletion procedure (2000).

FIG. 11 is a flow chart showing the class instance deletion operation.

Release the memory area of the instance (2
100).

The class indicated by the class pointer of the instance is released (2110).

FIG. 12 is a flow chart showing the operation of deleting an instance of the proxy class.

A message designating the instance deletion procedure by designating the instance identifier stored in the instance identifier field of the proxy instance is sent to the stub of the memory space indicated by the memory space identifier stored in the memory space identifier field. (2200).

The memory area of the proxy instance is released (2210).

The proxy class indicated by the class pointer of the proxy instance is released (2220).

FIG. 13 is a flow chart showing the class acquisition operation.

The class identifier is received (2300).

It is checked whether the class exists in the memory space (2310).

If it already exists, the instance number field is incremented by 1 (2320).

If it does not exist, a class area is secured in the memory space (2330), the instance number field is set to 1 (2331), and the class file corresponding to the class is read from the storage device (2332).

FIG. 14 is a flowchart showing the class releasing operation.

A reference to a class is received (2400).

The instance number field is decremented by 1 (2410).

It is determined whether the instance number field is 0 (2420). If it is 0, the class area is released (2430).

FIG. 15 is a flow chart showing the operation of the stub.

Wait for message to arrive (250
0).

Determine the type of message (251
0).

If the message is the instance generation, the class identifier is obtained from the message (2520), the class identifier is designated and the operating system is requested to generate the instance (2521).

If the message is another procedure, the instance identifier, the procedure name, and the input parameter are obtained from the message (2530), the procedure name and the input parameter are designated, and the procedure execution is requested to the instance indicated by the instance identifier (2531). ).

The execution result is sent as a response message (2540).

The message type is determined again, and if the instance is deleted, the process ends (2550).

[0084]

As described above, according to the present invention, since an object which operates by sharing a memory space can be operated in an independent memory space, data of an object user is not lost.

[Brief description of the drawings]

FIG. 1 is a block diagram showing one embodiment of the present invention.

FIG. 2 is a block diagram showing a class structure.

FIG. 3 is a flowchart of an application when creating an instance.

FIG. 4 is a flowchart of an operating system when creating an instance.

FIG. 5 is a flowchart of a class when creating an instance.

FIG. 6 is a flowchart of a proxy class when creating an instance.

FIG. 7 is a flowchart of an application when executing an instance.

FIG. 8 is a flowchart of a class when an instance is executed.

FIG. 9 is a flowchart of a proxy class when executing an instance.

FIG. 10 is a flowchart of an application when deleting an instance.

FIG. 11 is a flowchart of a class when deleting an instance.

FIG. 12 is a flowchart of a proxy class when deleting an instance.

FIG. 13 is a flowchart showing a class acquisition process.

FIG. 14 is a flowchart showing a class releasing process.

FIG. 15 is a flowchart showing a stub process.

[Explanation of symbols]

1 ... Calculator, 2 ... Storage Device, 110 ... Application, 210 ... Stub,
100, 200 ... Memory space, 120, 220, 13
0 ... Object, 121, 221, 131 ... Class, 125, 225, 135 ... Instance, 10
... memory space attribute table, 20 ... stub table,
33 ... Stub file, 30, 31,
32 ... Class file.

Claims (1)

[Claims] 1. A procedure in a memory space cannot access a procedure or data in another memory space, and a procedure in each memory space can communicate with a procedure in another memory space by a message. For each class in the object management system of an object consisting of a class that is a program for executing procedures for instances on a computer that can read the program and has multiple memory spaces, and a reference to the class and an instance that has data Register in the memory space attribute of the class whether the memory space of the instance generation request source program and the object is shared or not, set a proxy class corresponding to each class, set a stub that is a program corresponding to each proxy class, When requested to instantiate, If the memory space attributes of the lath are independent, a proxy instance that is an instance of the proxy class corresponding to the class is generated, and the proxy instance generates a new memory space as a stub memory space, and the stub corresponding to the class is generated. The proxy instance loads and executes the stub memory space, the proxy instance requests the stub to instantiate the class, the proxy instance stores the memory space identifier of the stub memory space and the instance identifier of the instance, and the proxy instance Of the proxy instance, and when the proxy instance is requested to execute the procedure, the proxy instance is configured to execute the procedure to the instance indicated by the instance identifier stored in the proxy instance. A message is sent to the stub of the memory space indicated by the memory space identifier stored in the stance, the response message is received and the result is returned, and when the proxy instance is requested to delete, the proxy instance remembers it. A message is sent to the stub in the memory space indicated by the memory space identifier stored by the proxy instance so as to delete the instance indicated by the instance identifier, the response message is received and the result is returned, and the stub terminates. The object management system, wherein the stub memory space also disappears, and when a failure occurs in the stub memory space, the generation element source program of the proxy instance continues processing.