Object management system and method for distributed object system

Claim 2

An object management method applicable to distributed object system, which includes at least one client computer at least one server computer, and at least one managing computer, the method comprising: providing the at least one server computer with a load balancing feature. obtaining object code and object data from the at least one managing computer in response to a remote object invocation from the at least one client computer, wherein said object code includes an attribute which indicates whether a read or a write is to be conducted during execution of a method defined by said object code, executing a requested method of the object on the at least one server computer; and performing object data overwrite on the at least one managing computer, when the attribute indicates that a write is to be conducted during execution of said method defined by said object code.

Claim 3

The method of claim 1 , comprising: at least one of activating objects and deactivating objects only on the at least one managing computer.

Claim 4

The method of claim 1 , comprising: performing senalized object invocation and method execution on the at least one server computer when a plurality of remote object invocations of a same object to execute a synchronized method of the object are issued from the at least one client-run computer.

Claim 5

The method of claim 1 , comprising: performing concurrent object invocation and method execution on the at least one server computer when a plurality of remote object invocations of a same object to execute a non-synchronized method of the object are issued from the at least one client-run computer.

Claim 6

The method of claim 1 , comprising: requesting the at least one managing computer to overwrite the object data and change the object data use flag when a write method is executed on the at least one server-run computer.

Claim 7

The method of claim 1 , comprising: performing both object data overwrite and object data use flag change on the at least one server computer when a read-only and non-synchronized method is executed on the at least one server-run computer.

Claim 8

The method of claim 1 , comprising: requesting the at least one managing computer to simply update the object data use flag when a read-only and synchronized method is executed on the at least one server computer.

Claim 9

The method of claim 1 , comprising: providing an object database containing catalog object and data and cart object and data.

Claim 10

A server computer, comprising: an object invocation unit; and a load balancing unit for selecting the server computer to perform a method execution task according to a load condition and for sending a request message to the object invocation unit of the selected server computer, wherein the object invocation unit receives the request message from the load balancing unit, sends a request for object code and object data to a managing computer, receives object code and object data from the managing computer, said object code includes an attribute which indicates whether a read or a write is to be conducted during execution of a method defined by said object code, executes the requested method, and sends object data fixed after said method has been executed and a request for object data overwrite to the managing computer, when the attribute indicates that a write is to be conducted during execution of said method defined by said object code.

Claim 11

A server computer, comprising: an object invocation unit; and a load balancing unit for selecting the server computer to perform a method execution task according to a load condition and for sending a request message to the object invocation unit of the selected server computer, wherein the object invocation unit receives the request message from the load balancing unit, sends a request for object code and object data to a managing computer, receives object code and object data from the managing computer, said object code includes an attribute which indicates whether a read or a write is to be conducted during execution of a method defined by said object code, executes the requested method, and sends object data fixed after said method has been executed and a request for object data overwrite to the managing computer, when the attribute indicates that a write is to be conducted during execution of said method defined by said object code.

Claim 12

A managing computer, comprising: an object access unit for receiving a request to obtain object code and object data from a server computer, obtaining object code from an object code table and obtaining object data from an object data table, said object code includes an attribute which indicates whether a read or a write is to be conducted dung execution of a method defined by said object code, sending the obtained object code and the obtained object data to the server computer, receiving object data fixed after said method has been executed and a request for object data overwrite, and writing object data fixed after said method has been executed over corresponding object data in the object data table, when the attribute indicates that a write is to be conducted during execution of said method defined by said object code; and an object manager unit for receiving a command to activate an object from an object management user program, retrieving the object from a database of executable-formed objects, registering object code into an object code table wherein object codes are stored, and registering object data into an object data into an object data table wherein object data are stored, wherein the object management user program provides at least one object activation command and at least one object deactivation command to the object manager unit, and wherein the database of executable-formed objects comprising the objects are represented as executable programs.

Claim 13

A managing computer, comprising: an object access unit for receiving a request to obtain object code and object data from a server computer, obtaining object code from an object code table and obtaining object data from an object data table, said object code includes an attribute which indicates whether a read or a write is to be conducted dung execution of a method defined by said object code, sending the obtained object code and the obtained object data to the server computer, receiving object data fixed after said method has been executed and a request for object data overwrite, and writing object data fixed after said method has been executed over corresponding object data in the object data table, when the attribute indicates that a write is to be conducted during execution of said method defined by said object code; and an object manager unit for receiving a command to activate an object from an object management user program, retrieving the object from a database of executable-formed objects, registering object code into an object code table wherein object codes are stored, and registering object data into an object data into an object data table wherein object data are stored, wherein the object management user program provides at least one object activation command and at least one object deactivation command to the object manager unit, and wherein the database of executable-formed objects comprising the objects are represented as executable programs.

Claim 14

A program for implementing an object management method in a distributed object system, the distributed object system including at least one client computer, at least one server computer, and at least one managing computer, the program when executed causes the distributed object system to perform the steps of: providing the at least one server computer with a load balancing feature; obtaining object code and object data from the at least one managing computer in response to a remote object invocation from the at least one client-run computer, wherein said object code includes an attribute which indicates whether a read or a write is to be conducted during execution of a method defined by said object code, executing a requested method of the object on the at least one server-run computer, and performing object data overwrite on the at least one managing computer, when the attribute indicates that a write is to be conducted during execution of said method defined by said object code.

Claim 15

A program for implementing an object management method in a distributed object system, the distributed object system including at least one client computer, at least one server computer, and at least one managing computer, the program when executed causes the distributed object system to perform the steps of: providing the at least one server computer with a load balancing feature; obtaining object code and object data from the at least one managing computer in response to a remote object invocation from the at least one client-run computer, wherein said object code includes an attribute which indicates whether a read or a write is to be conducted during execution of a method defined by said object code, executing a requested method of the object on the at least one server-run computer, and performing object data overwrite on the at least one managing computer, when the attribute indicates that a write is to be conducted during execution of said method defined by said object code.