JPH11232104A - Object update and management method and client/server system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an object update management method and a client/server system where retrieval of the location of the server is unnecessary every time of utilizing a service of the server to shorten the processing time required up to use of a server. SOLUTION: Service information indicating the location of a server 2 is registered in a service information register table 9, and information on a client is registered in a client register table 10. When service information is changed, a service information register means 6 retrieves the table 10 to report the change of service information to a client 1 using a pertinent service. When receiving a change report, the client 1 requests retrieval of the server to a trader 3. A service information retrieval means 7 retrieves the table 9 in accordance with a retrieval request and transfers the location of the server, who supplies the service designated by the client 1, to the client 1.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a server object update management method and a client / server system having an object update management function.

[0002]

2. Description of the Related Art Conventionally, an object service supporting collation between a service user (hereinafter, referred to as a client) and a service provider (hereinafter, referred to as a server) has been known as CORBA (Common Object Request Broker Arc).
hitecture)
Management Group (OMG: Object Management Grou
p).

FIG. 5 is a block diagram of a conventional client / server system conforming to such a Colva specification. This client / server system includes a client 21, a server 22, and a trader 23 for managing service information indicating the location of the server 22. The trader 23 includes a processing device 24 that operates under program control, and a storage device 25 that stores the service information. Further, the processing device 24
The storage device 25 stores the service information received from the server 22.
And a service information retrieving means 27 for retrieving service information stored in the storage device 25 in response to a request from the client 21. The storage device 25 stores service information. Has a service information registration table 29.

[0004] The service information registration means 26 is a server
When a service information registration request is issued from
Is registered in the service information registration table 29. When a service search request is issued from the client 21, the service information search unit 27 searches the service information registration table 29 and passes to the client 21 the location of the server that performs the service specified by the client 21. A plurality of entries (service information) are registered in the service information registration table 29. The service information includes a service type indicating a service type, a service attribute indicating a property of the service, and a server location indicating a location (address) of a server providing the service.

Next, such a client / server
The operation of the system will be described. The server 22 requests the trader 23 to register service information by designating the service type and service attribute of the service provided by the server 22 and the location of the server 22. The service information registration unit 26 of the trader 23 registers the service type, service attribute, and server location designated by the server 22 in the service information registration table 29 in response to the service information registration request from the server 22. Next, the client 21 specifies the service type and service attribute of the desired service, and searches for a server that provides the service by the trader 23.
Request to. Service information search means 27 of trader 23
Searches the service information registration table 29 using the service type and service attribute designated by the client 21 as keywords in response to a service search request from the client 21. Then, the service information search means 27
Finds service information having a service type and service attribute that match the keyword, and passes the server location in the service information to the client 21. Thus, the client 21 can obtain the location of the server 22 that provides the desired service, and can use the service provided by the server 22.

[0006]

In the client / server system described above, in order for the client to use the latest service, the client must search the server location every time the service is used. As a result, there is a problem that it takes time to use the server service. The reason that the location of the server must be searched every time the service is used is that there is no way for the client to know the update of the service. SUMMARY OF THE INVENTION The present invention has been made to solve the above problems, and an object of the present invention is to provide an object update management method and a client / server system that do not require searching for a server location every time a server service is used. And

[0007]

According to the object update management method of the present invention, as described in claim 1, client information relating to each object is prepared in advance in a trader, and when an object is changed, The change of the object is notified from the trader to the client relating to the object, and the client receiving the change notification requests the trader to search for the object. The change of the object is performed by the trader, for example, in response to a request from the server. At this time,
The trader notifies the client relating to the changed object of the object change, the client receiving the change notification requests the trader to search for the object, and the trader returns the corresponding object to the client. Further, as described in claim 2, the trader is:
Information of a client related to each object is stored in advance, and when a change occurs in an object managed by itself, the change of the object is notified to a client related to the object. Upon receipt of the request, the trader is requested to retrieve the object.

[0008]

Next, embodiments of the present invention will be described in detail with reference to the drawings. FIG. 1 is a block diagram of a client / server system showing an embodiment of the present invention. The client / server system according to the present embodiment manages a client 1, a server 2 for providing a service (for example, a translation service from Japanese to English) to the client 1, and service information indicating the location of the server 2. And a trader 3 for providing service information to the client 1 in response to a request from the client 1 and notifying the client 1 using the service of a change in the service information when the service information is changed. Have. The trader 3 includes a processing device 4 that operates under program control, and a storage device 5 that stores the service information and stores information of a client who is a user of a service registered as the service information.

Further, the processing device 4 stores the service information received from the server 2 in the storage device 5, and when the service information is changed, searches the client information of the storage device 5 and uses the corresponding service. Service information registering means 6 for notifying the client 1 of the change of service information, service information searching means 7 for searching service information stored in the storage device 5 in response to a request from the client 1, and client 1 And a client registration unit 8 for storing the client information received from the storage device 5 in the storage device 5. The storage device 5 includes a service information registration table 9 for storing service information and a client registration table for storing client information. 10
And

When a service information registration request is issued from the server 2, the service information registration means 6 registers the service information received from the server 2 in the service information registration table 9. As shown in FIG. 2, a plurality of entries (service information) are registered in the service information registration table 9. The service information includes a service type indicating a service type, a service attribute indicating a property of the service, and a location (address) of a server providing the service.
Which are stored in fields 11, 12, and 13, respectively. In addition,
The server location is, more precisely, the location of a program or a file that provides a service in the server 2. These programs or files are called objects.

When a service search request is issued from the client 1, the service information search means 7 searches the service information registration table 9 and passes the location of the server that performs the service specified by the client 1 to the client 1. When a user registration request from the client 1 occurs, the client registration unit 8
Is registered in the client registration table 10.

FIG. 3 shows the client registration table 10.
As shown in FIG. 7, a plurality of entries (client information) are registered. The client information includes a service type indicating the type of service used by the client, a service attribute indicating the nature of the service used by the client, and a client location indicating the location (address) of the client using the service. Are stored in fields 14, 15, and 16, respectively.

Next, the operation of the client / server system according to the present embodiment will be described. First, Client 1
Specifies the service type (eg, “translation”) and service attributes (eg, “Japanese to English”, “all versions”) of the desired service, and its own location (eg, pc01: writer). Requesting the trader 3 to register the user for the service.

The client registration means 8 of the trader 3
In response to a user registration request from the client 1, the service type, service attribute, and client location specified by the client 1 are registered in the client registration table 10 as shown in FIG. In FIG. 3, "version **" in the service attribute means all versions.

Next, the client 1 checks the service type (for example, "translation") and service attributes (for example, "Japanese to English", "latest version") of the desired service.
And requests the trader 3 to search for a server that provides the service. The service information search means 7 of the trader 3 responds to the service search request from the client 1 by using the service type and the service attribute designated by the client 1 as keywords as service information registration tables 9.
Search for.

When the service information retrieving means 7 finds service information having a service type and a service attribute that match the keyword, it passes the server location in the service information to the client 1. If there are a plurality of corresponding service information, a list of server locations in the service information is passed to the client 1.

Thus, the client 1 can obtain the location of the server 2 that provides the desired service, and based on the obtained server location, the server 2
Can be requested to provide services.

Next, the operation when the service provided by the server 2 is changed will be described with reference to FIG. When a service provided by itself is changed, the server 2 determines a service type (for example, “translation”) and a service attribute (for example, “Japanese to English”, “version 2.0”) of the service, Your location (for example, ws02: j
toe_2.0), and requests the trader 3 to register the service information.

The service information registration means 6 of the trader 3
In response to a service information registration request from the server 2, the service type, service attribute, and server
The location is registered in the service information registration table 9 (step 101 in FIG. 4). Subsequently, the service information registration unit 6 uses the service type and the service attribute designated by the server 2 as keywords as the client registration table 10.
(Steps 102 and 103).

When the service information registration means 6 finds client information having a service type and service attribute that match the keyword, the service information registration means 6 sends the service type (for example, “translation”) to the client 1 using the service. ) And a service attribute (for example, “Japanese to English”), and the change of the service information is notified (step 104).

That is, when a change occurs in the Japanese-to-English translation service provided by the server 2, the service information registration unit 6 registers the client 1 using this service in the client registration table 10. If there is, the client 1 is notified that the translation service has been updated based on the client location in the corresponding client information. The service information registration means 6
The above operations of steps 102 to 104 are repeated until all the client information has been checked.

The client 1 that has received the service information change notification requests the trader 3 to search for a server that provides the service specified by the change notification. That is, the client 1 specifies the service type ("translation") and the service attribute ("Japanese to English", "latest version"), and searches for a server that provides the service by the trader 3.
Request to.

By the same operation as described above, the server location is returned from the trader 3, so that the client 1 updates its stored server location with respect to the translation service to the location received from the trader 3. Thus, the client 1 can request the server 2 for the latest translation service updated from version 1.0 to version 2.0.

As described above, when the service provided by the server 2 is changed, the trader 3 notifies the client 1 using the service of the change of the service information. Server location may be updated accordingly.

That is, after first requesting the trader 3 to search the server from the client 1, the client 1 only needs to request the trader 3 to search the server when there is a notification of change of service information, and there is no change notification. In such a case, the server requests the server to provide the service based on the server location stored therein without requesting the server search. Therefore, according to the present invention, it is not necessary to search the server every time the service is used. In the present embodiment,
Although the client and server are singular, it goes without saying that there may be more than one client and server.

[0026]

According to the present invention, when a change occurs in an object, the client relating to this object is notified of the change in the object from the trader, so that the client first requests the trader to search for the object. After that, only when there is a notice of change of the object, it is sufficient to request the trader to search for the object, and it is not necessary to search for the object every time the service is used. As a result, the time required for using the server service can be reduced.

[Brief description of the drawings]

FIG. 1 is a block diagram of a client / server system showing an embodiment of the present invention.

FIG. 2 is a diagram showing a service information registration table.

FIG. 3 is a diagram showing a client registration table.

FIG. 4 is a flowchart illustrating an operation of a trader when an object is updated.

FIG. 5 is a block diagram of a conventional client / server system.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 ... Client, 2 ... Server, 3 ... Trader, 4 ... Processing device, 5 ... Storage device, 6 ... Service information registration means, 7
... Service information search means, 8 ... Client registration means,
9: service information registration table, 10: client registration table.

Claims (2)

[Claims] 1. An object update system in a client / server system comprising a client, a server providing services to the client, and a trader managing objects of the server and retrieving the object in response to a request from the client. A management method, in which information of a client related to each object is prepared in advance in a trader, and when a change occurs in an object, a change of the object is notified from the trader to a client related to the object, and the change notification is received. An object update management method, wherein a client requests a trader to search for an object. 2. A client / server system comprising a client, a server for providing services to the client, and a trader for managing objects of the server and retrieving the object in response to a request from the client. Information of a client related to an object is stored in advance, and when a change occurs in an object managed by itself, the change of the object is notified to a client related to the object. A client / server system for requesting a trader to retrieve an object when received.