JPH09330287A - Function asynchronous calling method of client server type system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable asynchronous calling without altering a program which is developed on the assumption of synchronous calling by providing a function call request mediating mechanism. SOLUTION: The function call request mediating mechanism 101a consists of a request reception part 201, a reply transmission part 202, a request transfer part 203, and a reply reception part 204. A request reception part 201 of a client receives a synchronous server function call message and stores it as request information in a request reply table 102. A request transfer part 203 for transfer to a server is a program module which requests message storage and distribution software to perform an asynchronous transfer process for the server function call message to server-side message storage and distribution software as to the server function call message received by a request reception part 201 of the client.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for asynchronously calling a function in a data processing system, and more particularly to a method for asynchronously calling a server function in a client-server type distributed data processing system.
More specifically, according to the present invention, the function asynchronous of the client-server type system which enables the asynchronous call of the server function without changing the client program and the server program created on the premise of the synchronous call of the server function. Regarding calling method.

[0002]

2. Description of the Related Art A client-server type is known as a data processing model in a distributed data processing system in which a plurality of data processing devices are connected by an information transmission network. Here, the server provides a data processing function. The client calls the data processing function of the server and requests processing according to the procedure for calling the function. In order to coordinate the function call of the client and the server, the client-server type system includes software for distributing the function call request of the client to the server.

The method of calling the data processing function can be roughly classified into two types: synchronous calling and asynchronous calling.

In the synchronous call method, when the client requests the “synchronous call request distribution software” to call the function of the server, the client waits until the functional processing is completed, and after receiving the processing result of the server from the “synchronous call request distribution software” as well. , The following processing is executed. Therefore, in the synchronous call, the processing result of the server is requested immediately, so if, for example, the computer in which the server exists is not running or there is a failure in the network route to the server, the synchronous function call will fail. The client is notified to that effect. Such a technique is disclosed in, for example, “The Common Object”.
Request Broker Architect
ure and Specification, OBJ
ECT MANAGEMENT GROUP and
X / Open, 1993 "pp. 81-81.

In the asynchronous call method, the client requests the "message storage and delivery software" to call the function of the server and the contents of the process, and executes the next process without waiting for the end of this function process. The processing requested by the client is normally stored in the "message storage unit" provided in the "message storage / delivery software". The server retrieves and executes the function call request from the "message storage unit", and stores the result again in the "message storage unit". The client inspects the "message store" and receives any desired results.

As described above, in the asynchronous calling method,
Since the processing result of the server is not requested immediately and the processing request is temporarily stored in the “message storage unit”, for example, even if the computer in which the server exists is not running or there is a failure in the network route to the server. The client can request processing. The basic technology for realizing this method is, for example, “DECmessageQ Int
production to Message Queui
ng, Digital Equipment Corpo
ration, 1994 ”.

In the following description, the synchronous call method means that the client call request process, the process by the called function of the server, and the process of obtaining the process result of the server by the client are continuous in time. Defined as a method of calling the server function that is executed as a unitary process. Further, the asynchronous call method is a server in which a client call request process, a process of a function called by a server, and a process of obtaining a process result of a server by a client are executed as independent processes in terms of time. Defined as a function calling method.

[0008]

Many of the application programs operating on the client-server type system are created by utilizing the synchronous calling method. However, in order to use these programs comfortably in an environment through a network that is not always connected, or in an environment where a computer that has a server is not running, the method of requesting a function for the server is changed from synchronous call to asynchronous Need to change to call.

However, the procedure of function call is different between the synchronous call and the asynchronous call, and it is not easy to change the program. In particular, in the case of the synchronous call method, the client side called and obtained the result with a single request to the "synchronous call request distribution software". 2 of "request" and "acquisition of results"
You need to change the program to make one request. Furthermore, when it is necessary to wait for the time to obtain the result, it is necessary to change the program to handle it.

An object of the present invention is to provide an asynchronous invocation method for a client-server system which enables an asynchronous invocation of a server function by a client without modifying a client program and a server program developed on the premise of synchronous invocation. To do.

[0011]

In a first method for asynchronously calling a function of a client-server type system according to the present invention, at least one client computer and at least one server computer are connected to each other via a network, and the client computer described above is connected. Is a server that includes a client program for transmitting a server function call message to the server computer, and the server computer receives the server function call message from the client computer and executes the contents instructed in the server function call message in a synchronous state. It is applied to a client-server type system provided with a program and has the following features.

That is, the client program in the client computer has a first step of transmitting the server function call message, and the first program receives the server function call message and stores the contents in a table. Then, the server function call message is asynchronously transmitted to the network, and the server reply message from the server computer for the server function call message is asynchronously received via the network, and both are stored in the above table in association with each other. When the server function call message is received,
Referring to the above table, when at least one of the contents of the server function call message and the server reply message for the server function call message is not stored, it is determined that the synchronous call to the server computer has failed for the client program. When a server reply message with the contents is sent and both the contents of the server function call message and the server reply message for the server function call message are stored, the server reply message obtained from the table is sent to the client program. The second step of transmitting and the second program asynchronously receive the server function call message via the network, and receive the received server function call message. The third step of transmitting to the server program of the computer, further receiving the server reply message transmitted from the server computer, and asynchronously transmitting to the network, and the client program of the client computer receives the server function call message. The fourth step is to call and execute the function specified by the server function call message, create a server reply message, and send it to the second program.

In the second method for asynchronously calling a client-server type system according to the present invention, at least one client computer and at least one server computer are connected to each other via a network, and the client computer is a server function for the server computer. The server computer includes a client program for transmitting a call message in a synchronous state, and the server computer includes a server program for receiving a server function call message from the client computer and executing the contents instructed in the server function call message in a synchronous state. It is applied to a client-server type system and has the following features.

That is, the client program in the client computer sends the server function call message in the first step, and the server function call message intermediary mechanism provided in the client computer sends the server function call message. It is determined whether or not the information included in the server function call message is already stored in the request reply table provided in the client computer, and if it is determined that the information is not stored, A server reply message having the content that the synchronous call to the server computer has failed is sent to the client program, and the information included in the server function call message is stored in the request reply table, and the server Sends a function call message,
Further, when it is determined that the information is stored,
It is determined whether the server reply message corresponding to the server function call message from the server computer is stored in the field corresponding to the field in which the information included in the server function call message is stored. If it is determined that it is stored, the above server reply message is sent to the client program, and if it is determined that the server reply message is not stored, the client program is synchronized with the server computer. The second step of transmitting a server reply message containing the failure of the call, and the message storage / delivery software provided in the client computer are transmitted from the server function call message mediation mechanism in the second step. The third step of receiving the server function call message that has been received, and asynchronously transmitting the received server function call message to the target server computer via the network, and the message storage and distribution software provided in the server computer. And a fourth step of asynchronously receiving the server function call message transmitted from the message storage and distribution software in the client computer in the third step and transmitting it to the server function call message intermediary mechanism provided in the server computer. The server function call message intermediary mechanism provided in the server computer receives the server function call message transmitted from the message storage / delivery software provided in the server computer in the fourth step, and receives the server function call message in the server computer. The server function call message sent in the fifth step, and the function specified in the server function call message is received by the server program provided in the server computer. Is executed to create a server reply message and send it to the server function call message intermediary mechanism of the server computer, and the server function call message intermediary mechanism provided in the server computer is In the sixth step of receiving the server reply message transmitted from the server program in the step of (4) and transmitting it to the message storing and delivering software in the server computer, the message storing and delivering software provided in the server computer is the sixth step. In the step of The seventh step of receiving the received server reply message and transmitting the server reply message asynchronously received via the network to the target client computer, and the message storage and distribution software provided in the client computer are An eighth step of asynchronously receiving a server reply message transmitted from the message storage / delivery software in the server computer through the network in the seventh step and transmitting the server reply message to the server function call message intermediary mechanism provided in the client computer And the server function call message intermediary mechanism provided in the client computer, receives the server reply message transmitted in the eighth step, and stores it in the request reply table in the client computer. Kicking is characterized in that it is composed of a ninth step of storing the column to the server reply message corresponding to the column information about the server function call included in the server reply message is stored.

A third function asynchronous invocation method for a client-server type system of the present invention is a library linked by a server function invocation message intermediary mechanism provided in the client computer according to the second aspect when a client program is compiled. When the client program sends a server server function call message, the main body of the client program selects the server function call message intermediary mechanism in the library.

According to a fourth aspect of the present invention, there is provided a method for asynchronously calling a function of a client-server type system, wherein in the second or third aspect of the invention, the server function call message intermediary mechanism in the second step is the client computer. Holds the information of the server function call message in association with the valid period of the server function call preset by the user, and before sending the server reply message to the client program, the current time is the valid period described above. It is characterized in that a step of determining whether or not it is inside is provided.

According to a fifth aspect of the present invention, a method for asynchronously calling a client-server type system, in the second, third or fourth aspect of the present invention, the server function call message mediation mechanism in the second step comprises: Before sending the server reply message to the client program, a step of presenting a part of the contents of the server reply message to the user and receiving an input regarding acceptance or rejection of the server reply message by the user is provided. .

A sixth client-server system function asynchronous invocation method of the present invention is the server function invocation message intermediation mechanism in the second step in the second, third, fourth or fifth invention. In the processing, when the client computer holds symbols such as character strings and graphics for the server function call message preset by the user and presents the server reply message and a part of the content to the user. It is characterized in that a step of presenting the symbols such as the character strings and figures at the same time, or presenting the symbols such as the character strings and figures instead of presenting the server reply message and presenting part of the contents thereof is provided. .

In a seventh method of asynchronously calling a client-server system according to the present invention, at least one client computer and at least one server computer are connected to each other via a network, and the client computer functions as a server to the server computer. The server computer is provided with a synchronous call request distribution software and a client program necessary for transmitting the call message, and the server computer receives the server function call message from the client computer and displays the contents instructed by the server function call message. It is applied to a client-server type system provided with a synchronous call request distribution software and a server program necessary for execution, and has the following features.

That is, the client computer has the first step of transmitting a server function call message to the network by the action of the client program in the client computer and the synchronous call request distribution software, and the first computer has the first step. By the function of the synchronous call request distribution software provided in the computer, the server function call message transmitted in the first step is received, and further, by the function of the naming function program provided in the first computer, The name identifier table provided in the first computer is searched based on the call function name included in the received server function call message, and the address of the server function call message intermediary mechanism provided in the second computer is obtained. Furthermore, on By the function of the synchronous call request distribution software, the second step of transmitting the server function call message to the server function call message intermediary mechanism provided in the second computer at the address via the network, and the second step. The calculator
By the function of the synchronous call request distribution software provided in the second computer, the server function call message transmitted at the second step receives the server function call message from the network, and the server function call message mediation mechanism at the above address It is determined whether or not the information included in the server function call message is already stored in the request reply table provided in the computer, and if it is determined that the information is not stored, the client computer A server reply message indicating that the synchronous call to the server computer has failed for the client program is transmitted via the network by the operation of the synchronous call request distribution software provided in the second computer, and the server Function call Information contained in the message is stored in the request reply table, and the server function call message is asynchronously transmitted to the third computer by the action of the message storage / delivery software provided in the second computer, and the information is further transmitted. Is stored, the server reply message corresponding to the server function call message from the server computer is stored in the field corresponding to the field storing the information included in the server function call message. If it is determined that the server reply message is stored, the server reply message is called to the client program of the client computer by the synchronous call provided in the second computer. Request distribution software works When it is determined that the server reply message is not stored, the synchronous call request distribution software provided in the second computer causes the client computer program of the client computer to operate. , A third step of transmitting a server reply message containing the fact that the synchronous call to the server computer has failed through the network, and the third step.
The message storage / delivery software provided in the computer of the second computer asynchronously receives the server function call message transmitted from the message storage / delivery software of the second computer in the third step via the network, and The server function call message intermediary mechanism provided in the computer transmits the message, and the server function call message intermediary mechanism provided in the third computer receives the server function call message and provides it in the third computer. By the action of the synchronous call request distribution software provided, the fourth step of transmitting the server function call message to the network, and the synchronous call request distribution software provided in the server computer are transmitted in the fourth step. Server function call message Message via the network, the server program provided in the server computer calls and executes the function specified by the server function call message, creates a server reply message, and calls the server server's synchronous server function. The fifth step of transmitting to the network via the message distribution software, and the synchronous call request distribution software provided in the third computer receives via the network the server reply message transmitted in the fifth step. Then, by the function of the server function call message mediation mechanism provided in the third computer, the message storage delivery software provided in the third computer is transmitted to the message storage delivery software provided in the third computer. The server reply message The sixth step of receiving and transmitting asynchronously to the message storage / delivery software in the second computer via the network, and the message storage / delivery software provided in the second computer are In the step of step 3, the server reply message transmitted from the message storage / delivery software in the third computer is received asynchronously, and the server function call message intermediary mechanism provided in the third computer acts to cause the request reply table to be stored. A seventh step of storing the server reply message in a field corresponding to a field in which information related to a server function call included in the server reply message is stored
It is characterized by being composed of steps and.

According to the first, second, third, and seventh client-server system function asynchronous invocation methods, when the server function synchronous invocation message is transmitted from the client program and the server function synchronous invocation message is received. , The contents of the function synchronous call message and the contents of the server reply message which is the response from the server computer corresponding to the function synchronous call message are judged to be stored in the table (request reply table) As a result, the server reply message is edited and transmitted as information including the success or failure of the function call. The process of receiving the server function synchronization call message from the client program and the process of transmitting the server reply message to the client program are performed in synchronization.

However, the transmission of the server function synchronous call message to the server computer and the transmission of the server reply message from the server computer are performed asynchronously.

As a result, the client computer can call the server function asynchronously without changing the client program and the server program developed on the premise of synchronous calling.

According to the fourth method for asynchronously calling the function of the client-server type system, whether or not the server reply message is valid at the current time is checked based on the valid period of the server function call preset by the user. This makes it possible to prevent the client program from receiving an old server reply message that has expired.

According to the fifth function of the client-server type system asynchronous invocation method, before transmitting the server reply message to the client program, a part of the contents of the server reply message is presented to the user and used. Since it becomes possible to receive an input regarding acceptance or rejection of the server reply message by a person, it is possible to reduce the possibility that the client program receives the unjust server reply message and performs the unjust process. Further, according to the fifth function asynchronous invocation method of the client-server type system, when the server reply message obtained by the asynchronous server function invocation is received in the processing by the function invocation request mediation mechanism, the contents thereof are previously described. Since a part of the above is presented to the user, the user can start the client program at an appropriate time.

According to the sixth function asynchronous invocation of the client-server type system, when presenting a server reply message or a part of its contents to the user, the symbols such as the character strings and figures are presented at the same time. Alternatively, instead of presenting the server reply message or presenting a part of the contents thereof, the symbols such as the character strings and figures are presented, so that the user can easily understand the contents of the server reply message.

[0027]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The embodiments shown in the drawings will be described below in more detail. Note that the present invention is not limited to the embodiment described below.

(First Embodiment) FIG. 1 is a block diagram showing an example of the configuration of a client-server type system to which the function asynchronous invocation method for a client-server type system according to the present invention is applied.

In the client-server system 100 shown in FIG. 1, a plurality of computers 109a and 100b (other computers are not shown) are connected to a LAN (Local Area N).
It has a configuration in which it is connected by a network 108 for transmitting information such as an "etwork".

On the computer 109a, the client program 105 and the function call request mediation mechanism 101
a, the request reply table 102, and the message storage / delivery software 104a are arranged, and the computer 10
A server program 107, a function call request mediation mechanism 101b, and message storage / delivery software 104b are arranged on 9b. Therefore, the computer 109a is used as a client and the computer 10
9b is used as a server.

In FIG. 1, the client program 1
05 is a server program 107 in the procedure of synchronous call.
Is a program that calls the function of.

Message accumulation / delivery software 104
a and 104b are accumulating messages inside,
It is a program for communicating with each other via the network 108 and delivering messages to each other.

The server program 107 is a program that receives a function call in the procedure of calling a synchronous call.

FIG. 2 is an explanatory diagram showing an example of a server function call message (function call request) 301 used in the client-server type system of FIG. The server function call message 301 is sent from the client program shown in FIG. 1 to the function call request mediation mechanism (client side) 101a.

As shown in FIG. 2, the server function call message 301 includes request information 210. The request information 210 includes a server identifier 211 and a function identifier 2
12 and an argument sequence 213. The server identifier 211 is information for identifying a server program when a function is called, and is, for example, a UUID (Universal Unal) assigned to each server program.
and an address on the network of a computer in which the server program exists. The function identifier 212 is information uniquely attached to each function provided by the server for identifying the function. The argument list 213 is a list of arguments when the function is called. As described above, the server function call message 301 is composed of sufficient information for function call from the server.

FIG. 3 is an explanatory diagram showing an example of the server reply message 401 used in the client-server type system of FIG. Server reply message 401
Is a function call request mediation mechanism (on the server side) after the server program shown in FIG. 1 has completed the requested processing.
It is sent to 101b.

The server reply message 401 includes reply information 220 and request identification information 420. The reply information 220 includes a return value array 221 and a success notification flag 412. Request identification information 42
0 is, for example, the server identifier 211 and the function identifier 212.
And request list 210 including the argument list 213
(See FIG. 2) can be identified. As another embodiment of the request identification information 420, a unique number may be attached to each request and used as the request identification information 420.

FIG. 4 is a diagram showing details of the function call request mediation mechanism 101a and the request reply table 102 on the client side shown in FIG. The function call request mediation mechanism 101 a uses the server function call message 301 from the client program 105.
Request reception unit 201 that receives a request, a reply transmission unit 202 that sends a server reply message 401 to the client program 105, a request transfer unit 203 that transfers request information 210 to the server, and a reply that receives reply information 220 from the server. Receiver 2
04.

In FIG. 4, the request receiving unit 201 of the client is a program module that receives the synchronous server function call message 301 as described above. This is because in the configuration shown in FIG. 1, a synchronous server function call message 301 is received,
Request information 2 in the request reply table 102
It is stored as 10.

In FIG. 4, the request transfer unit 203 to the server is the request reception unit 2 of the client.
Server function call message 3 received at 01
01 is a program module that requests the message storage / delivery software 104a to asynchronously transfer the server function call message 301 to the server-side message storage / delivery software 104b.

Further, in FIG. 4, the reply receiving unit 204 of the server receives the server reply message 4 sent from the message storing and delivering software 104b on the server side.
01 is received via the message storage / delivery software 104a on the client side and is stored in the request reply table 102. Further, in FIG. 4, the reply sending unit 202 to the client sends the client server reply message 401 received from the server by the reply receiving unit 204 of the server as a return value after receiving the server function call of the client program 105. 1
It is a program module to be sent to 05.

As described above, in FIG. 4, the request transfer unit 203 to the server has the request information 210.
The (server function call message 301) is transferred as asynchronous information to the message storage / delivery software 104a shown in FIG. The request receiving unit 201 of the client and the request transferring unit 203 to the server can be realized as follows in addition to the above configuration. For example, the client program 10
5, the function call request mediation mechanism 101a is configured as one of the libraries to be linked at the time of compilation, and the main body of the client program 105 executes the function call request mediation mechanism 101a in the library when executing an asynchronous server function call. It can be realized by making it selectable. By embedding the function call request mediation mechanism 101a in the message storage / delivery software 104a, the request reception unit 201 of the client can receive the server function call message 301 shown in FIG.

Further, as shown in FIG. 4, the request reply table 102 is composed of a set of request information 210 and reply information 220. The request information 210 is composed of a “server identifier 211” used when designating a server when calling a function, a “function identifier 212” used when designating a function, and an “argument list 213” passed when calling a function. ing. The reply information 220 is “return value sequence 2 which is the result of the function call.
21 ”and a“ success notification flag 412 ”indicating success or failure of the function call. The request reply table 102 is stored as a file, for example.

The server-side function call request mediation mechanism 101b uses the server-side message storage / delivery software 104b to send a server function call message 301.
Is received, the server function is called according to the contents in a synchronous calling procedure, a server reply message 401 is generated from the calling result, and the server reply message 401 is transferred to the client side message storage / delivery software 104a. Distribution software 104b
Is a program to ask.

Next, the processing procedure in the function call request mediation mechanism 101a on the client side will be described in detail with reference to the flowchart shown in FIG.

The request receiving unit 201 of the function call request mediation mechanism 101a on the client side receives the server function synchronous call message 301 (request) from the client program 105 (step 5).
01). Subsequently, the request receiving unit 201 checks whether or not the server identifier 211, the function identifier 212, and the argument list 213 in the received server function synchronization call message 301 are recorded in the request reply table 102 (step 502).

When the same reserver function synchronous call message 301 (request) is not recorded (step 502), the reply transmission unit 20 to the client
2 sends a reply to the client program 105 to the client, which means a call failure (step 503), and the request transfer unit 203 to the server
Then, the column is added to the request reply table 102 and the request information 210 is written (step 5
04), assemble the server function call message 301, request the message storage / delivery software 104a to deliver this message (step 505), and end the processing. The transmission of the reply to the client program 105, which means that the call has failed, is performed (step 503), for example, by transmitting the reply in which the success flag 412 in the server reply message 401 is set to “failure”.

If the same server function synchronous call message 301 (request) is recorded in step 502, whether the reply information 220 corresponding to the request exists in the request reply table 102 in the reply sending unit 202 to the client. It is checked whether or not (step 511). If it exists, the reply information 220 is read, a server reply message is created (step 512), a reply is sent to the client (step 513), and the process is ended.

If the reply information 220 corresponding to the request does not exist in step 511, the reply indicating the call failure is transmitted to the client (step 5).
21), end the process. Client program 10
The reply transmission (step 521) meaning that the call to the server 5 is unsuccessful is performed by, for example, the server reply message 40.
This is done by transmitting a reply in which the success flag 412 in 1 is set to "failure".

FIG. 6 is a flowchart showing a processing procedure in the reply receiving unit 204 (see FIG. 4) from the server existing in the function call request mediation mechanism 101a on the client side.

The processing in the reply receiving unit 204 from the server is performed, for example, by the message storage / delivery software 1
Notification of message arrival from 04a, computer 109a
It starts by the interruption by the "timer interruption" provided by. The process of the reply receiving unit 204 from the server is
First, from the message accumulation / delivery software 104a,
The server reply message 401 (see FIG. 3) is received (step 601), and the request reply table 1
02, server reply message 401 received
Search the column with the request corresponding to (step 60
2) The reply information 220 is written in that column (step 603), and the process is terminated. In step 602 of searching for a column of the corresponding server reply message 401, the server identifier 211 and the function identifier 212 in the server reply message 401 are compared with the server identifier 211 and the function identifier 212 in the request reply table 102, respectively. It

FIG. 7 is a flowchart showing a processing procedure in the function call request mediation mechanism 101b on the server side. The function call request mediation mechanism 101b first receives the server function call message 301 from the message storage / delivery software 104b (step 701). Next, the server function is synchronously called based on the information obtained from the server function call message 301, and a reply such as a return value of the function call result is waited for (step 702). Next, after obtaining the reply, a server reply message 401 (see FIG. 3) is created from the reply information, and the server reply message 401 is distributed to the client side message distribution software 104a. After requesting the software 104b (step 703), the process ends.

FIG. 8 is an explanatory view showing the procedure of the asynchronous call in the above-mentioned first embodiment. The client program 105, the function call request mediation mechanisms 101a and 105b, the message storing and delivering software 104a and b, and the server program. A typical example of mutual connection between 107 is shown.

As shown in FIG. 8, the first server function synchronous call of the client program 105 (801)
Then, the function call request mediation mechanism 101a sends a reply of call failure to the client program 105. Therefore, from the perspective of the client program 105, it looks as if the synchronous call failed.

However, in reality, the function call request mediation mechanism 101a transmits request information (server function call message 301) to the message storage / delivery software 104a, and the message storage / delivery software 104a asynchronously stores the message on the server side. Request information (server function call message 301) is transmitted to the distribution software 104b.

Then, the server-side message storage / delivery software 104b transmits the received request information to the function call request mediation mechanism 101b, and makes a synchronous call of the server function to the server program 107. As a result, the server program 107 transmits reply information (server reply message 401) to the function call request mediation mechanism 101b (80
2). The function call request mediation mechanism 101b
Sends the received reply information to the message storing and delivering software 104b, and the message storing and delivering software 104b asynchronously transfers it to the client side message storing and delivering software 104a.

Next, the message storage / delivery software 104a on the client side transfers the received reply information to the function call request mediation mechanism 101a, and stores the contents in the request reply table 102.

When the client program 105 executes the second server function synchronous call (803), the function call request mediation mechanism 101a reads the corresponding reply information from the request reply table 102 and sends it to the client program. Therefore,
The second call to the server function synchronization (803) has been successfully called from the viewpoint of the client program 105.

As is apparent from the above description, in the first server function synchronous call (801) of the client program 105, the client program 105 looks as if the synchronous call failed. However, the function call request mediation mechanism 101
a, 101b and message storage / delivery software 104
By the above operations of a and 104b, the synchronous call of the server function is executed at another timing (802), and the result is passed to the function call request mediation mechanism 101a. Therefore, in the subsequent server function synchronous call (803) by the client program 105, even if the function of the server program 107 cannot be synchronously called, the client function 105 is returned by returning the result of the server function synchronous call (802). From the perspective, it seems that the call was successful.

According to the above-described first embodiment, the function call request mediation mechanism 101a for receiving the synchronous server function call and outputting it as the asynchronous server function call to the message storage / delivery software is provided. The invention is not limited to this, and the function call request mediation mechanism can be realized as follows. For example, when a function call request mediation mechanism is configured as one of the libraries to be linked at the time of compiling the client program 105, and the main body of the client program 105 executes the function call request mediation in the library when executing an asynchronous server function call. This can be realized by making the mechanism selectable. Further, the function call request mediation mechanism 101a is used as the message storage / delivery software 1
By embedding it in 04a, the request receiving unit 201 of the client can receive the server function call message 301 shown in FIG.

(Second Embodiment) FIG. 9 is a block diagram showing an embodiment in which the present invention is applied to a client-server type system having a naming function. In the client-server system 900 shown in FIG. 9, a plurality of computers 109c, d, e, f, g are connected to a LAN (Local).
(1 Area Network) and the like, and is connected via an information transmission network 108. Computer 10
The client program 105 and the synchronous call request distribution software 901c are arranged on the 9c. A server program 107 composed of a plurality of functional programs and a synchronous call request distribution software 901d are arranged on the computer 109d. Further, a naming function 902, a name identifier table 903, and a synchronous call request distribution software 901d are arranged on the computer 109e. Further, on the computer 109f, a function call request mediation mechanism (client side) 101
a, the request reply table 102, the message storage / delivery software 104a (client side), and the synchronous call request delivery software 901a are arranged. Also, on the computer 109g,
Function call request mediation mechanism (server side) 101b
And message storage / delivery software (server side) 104
b and synchronous call request distribution software 901b
And are arranged respectively. Therefore, computer 1
09c is used as a client and computer 109d
Is used as a server.

The greatest feature of the second embodiment shown in FIG. 9 is that the function call request mediation mechanism (client side) 101a and the request reply table, which are arranged in the client computer in the first embodiment. 102 and message storage / delivery software 104a
Computer 1 that is not the client (client side)
09f, and the function call request intermediary mechanism (server side) 101b and the message storage / delivery software (server side) 104b, which were arranged in the computer of the server in the first embodiment, are arranged in the computer 109g that is not the server. That is the point.

FIG. 10 is a diagram showing an example of the structure of the name identifier table 903 provided on the computer 109e shown in FIG. The name identifier table 903 shows the function name 10
01 and a function identifier 211 are associated with each other.
Synchronous call request delivery software 901a,
Function program name 1001 that configures the server program 107 that b, c, d and its application programs attach for convenience
And a set of function identifiers 211 corresponding to the names. As described above, the server program 107
Is usually composed of a plurality of function programs, and each function program is given a name. Also,
Synchronous call request delivery software 901a,
b, c, and d are programs that deliver request messages to each other via the network 108.

The naming function 902 provided on the computer 109e receives the function program name 1001 from the synchronous call request distribution software 901a, b, c, d.
Is a program that returns a function identifier 211 by referring to the name identifier table 903 also provided on the computer 109e when called with an argument.

In this embodiment, for the function to be asynchronously called, the function name is stored as the function program name of the name identifier table 903, and the function call request mediation on the computer 109f is used as the function identifier of the name identifier table 903. The address of the mechanism 101a is stored.

Here, unlike the first embodiment, the request receiving unit (not shown, corresponding to 201 in FIG. 4) in the function call request mediation mechanism (client side) 101a compiles the client program 105. As one of the libraries that are sometimes linked, function call reconfiguration and message storage / delivery software 10
For example, the function call request mediation mechanism 101, which is one independent program, is not embedded in the 4a.
It is a program module included in a.

The processing procedure of the first embodiment is different from the processing procedure of the client-side function call request mediation mechanism 101a in FIG. 5 in the server function synchronous call reception processing (step 501) (others). The process is basically the same as that of the first embodiment, and the process corresponding to the seventh invention (the invention according to claim 7) described in the section of the means for solving the problems is executed.) . That is,
In the first embodiment, the request receiving unit 201 in the function call request mediation mechanism 101a is configured as a library to be linked at the time of compiling the client program 105, or is embedded in the message storage / delivery software 104a. The server function call message 301 transmitted by the client program 105 is directly received. However, in the second embodiment, the request receiving unit of the client is included in the function call request mediation mechanism 101a which is one independent program. Since the function identifier 211 of the name identifier table 903 holds the identifier (address) of the function call request mediation mechanism 101a, not the true identifier of the function program to be called, the server function call message of the client program 105 is stored. 301 is
Sent to the function call request mediation mechanism 101a,
Function call request mediation mechanism (client side) 1
The request receiving unit in 01a receives the server function call message 301.

According to the second embodiment described above, the client program 105 and the server program 107 created on the premise of the synchronous function call are not modified, and the message storage / delivery software 1 is used.
The client program 105 can make an asynchronous function call request of the server program without making any changes to 04a and 104b. Moreover,
Even when a plurality of computers serving as servers are provided in addition to the computer 109c, asynchronous calls can be executed from the computers serving as the servers.

(Third Embodiment) A third embodiment described below
In the embodiment, in the first embodiment, a means for notifying the user of acquisition of reply information, a means for confirming the reply contents at the time of reply transmission, and a symbol (character or figure) for calling the server function ( Means of giving a nickname)
An automatic management means for the expiration date of reply information and a means for setting a failure reply pattern are added.

FIG. 11 shows an example of the configuration of a client-server system to which the function asynchronous invocation method of the client-server system of the present invention is applied (third embodiment).
FIG. That is, the client-server type system 1100 shown in FIG. 11 is the computer 10 of the client-server type system 100 according to the first embodiment.
9a (see FIG. 1), the auxiliary information table 1102,
An auxiliary information table management program 1121 and a keyboard 1122 are additionally arranged, and further, the computer 109a
The display device 1124 and the on-screen point instruction device 1125 are connected via the screen display adapter 1123. Further, instead of the request reply table 102 of the first embodiment, a new request reply table 1301 is provided by expanding the request reply table 1021. It is configured by arranging.

FIG. 12 is a diagram showing details of the structure of the auxiliary information table 1102 shown in FIG. As shown in the figure, the auxiliary information table 1102 includes the target server function 12
01, a failure reply pattern 1202, a reply information valid period 1203, and a nickname of a call (a symbol such as a character or a figure) 1204. The column of the target server function 1201 is the server identifier 21.
1 and a function identifier 212, and is composed of information capable of designating a specific function call from a specific server.

The column of reply pattern 1202 at failure consists of a set of a plurality of return values, and is composed of information capable of creating a reply message of a specific pattern. The reply information storage period 1203 field is configured to hold designation information for the number of days and time. The column of the nickname for calling (a symbol such as a character or a figure) 1204 is configured to hold an arbitrary character string or graphic information. The auxiliary information table 1102 is stored as a file, for example.

The auxiliary information table management program 1121 shown in FIG. 11 is capable of rewriting the auxiliary information table 1102 and investigating the contents, and displays various figures and characters on the screen to the screen display adapter 1123. It is configured so that it can be requested. In addition, the auxiliary information table management program 1121 uses the screen display adapter 1123.
It is a program for receiving the positional information on the screen pointed by the on-screen point indicating device 1125 sent from the user and the input information of the user sent from the keyboard 1122.

Screen display adapter 1123 shown in FIG.
Is configured to receive screen display requests for various graphics and characters, hold graphic pattern information to be displayed on those screens, and generate a display device control signal for displaying the graphic patterns. Also, the on-screen point indicating device 1
Sending a signal to 125, or pointing device 11 on the screen
25 is a device that processes a signal sent from the device 25 and calculates position information on the screen pointed by the on-screen point pointing device 1125.

The display device 1124 shown in FIG.
Is a device for receiving a display device control signal and displaying a graphic pattern on the screen according to the control signal.

The keyboard 1122 digitizes the character input information of the user of the computer 109a and converts it into the computer 10
It is a device for notifying 9a.

FIG. 13 is a diagram showing a configuration example of the request reply table 1301 in the third embodiment shown in FIG. Request reply table 130
1 is configured to hold a request acceptance date and time 1302 in addition to the configuration of the request reply table 102 (see FIG. 4) of the first embodiment. The request reception date and time 1302 column includes, for example, the year, month, and
It is composed of a set of integer values representing the information of day, hour and minute.

FIG. 14 is a flow chart showing a processing procedure in the function call request mediation mechanism 101a on the client side in the third embodiment shown in FIG. 14, the same steps as those shown in FIG. 5 are designated by the same reference numerals. The processing procedure of the request mediation mechanism 101a in the third embodiment is shown in FIG.
The following steps are different from the processing procedure of the first embodiment shown in FIG. That is, step 1401 of determining whether the function is the target server function, and steps 1402 and 140 of transmitting a call failure reply to the client.
8, a step 1403 of adding a column to the request reply table and writing the request content, a step 1404 of transferring the synchronous call request to the server, a step 1405 of checking the reply content, and a step 1407 of checking the expiration date of the reply. The step 1406 of deleting reply information is different.

That is, the step 1401 of judging whether the function is the target server function is a step executed immediately after the reception of the server function synchronous call (step 501), and the server identifier 211 in the server function call message 301.
And the function identifier 212 and the server identifier 211 and the function identifier 212 in the target server function 1201 column in the auxiliary information table 1102 are compared to determine whether the target server function is registered.

In step 1402 of transmitting a call failure reply to the client, the server function call message 3 of the client received in step 501 is sent.
Server identifier 211 and function identifier 212 included in 01
And the target server function 12 in the auxiliary information table 1102
The server identifier 211 in the 01 column and the function identifier 212 are compared, a corresponding failure reply pattern is found, a server reply message 401 is created based on this information, and it is sent to the client.

Addition of fields to the request reply table and writing of request contents In step 1403, in addition to the processing of step 504 of the first embodiment, the date and time when the server function call message 301 of the client is accepted is set, for example, in the computer. Is added to the request reply date and time 1302 field of the request reply table 1301 with reference to the clock.

In the step 1404 of transferring the synchronous call request to the server, the function call received in the server function synchronous call reception (step 501) is not registered in the auxiliary information table 1102, and the function call request mediation mechanism 101a is operated thereafter. This is a step that is called when the processing step of step 1 is not executed and directly transfers the server function call message 301 to the server program 107 on the computer 109b.

Step 1 for confirming the expiration date of the reply
407, reading reply information (step 512)
Based on the reply information valid period 1203 of the auxiliary information table 1102, the request acceptance date and time 1302 of the request reply table 1301, and the current time obtained from the clock in the computer 109a, for example. , A step of determining whether or not the reply information is still valid. If the expiration date has passed, the reply information is erased (step 1406), and if it has not passed, the reply information is read (step 512).

The reply content confirmation step 1405 is a step executed immediately after reading the reply information (step 512), and compares the server identifier 211 and the function identifier 212 to obtain the server function of the client received in step 501. Call message 30
The request acceptance time 1302 corresponding to 1 is obtained from the request reply table 1301, and the nickname of the call (a symbol such as a character or a figure) 1204 is obtained from the auxiliary information table 1102.
Request that the requested information be displayed, and accept the user's input.

FIG. 15 shows the reply content confirmation step 14
In 05, the auxiliary information table management program 112
FIG. 3 is a diagram showing a display example that 1 requests the screen display adapter 1123. Each of columns 1501 to 1508 has a request acceptance date / time 1302, a nickname of a call (a symbol such as a character or a figure) 1204, a server identifier 211, a function identifier 212, and an argument arrangement 213.
The return value sequence 221 is displayed. Further, areas 1510 and 1511 in which “Yes” and “No” are displayed are provided in order to accept the input of the user. The user inputs the confirmation of the reply contents, for example, by obtaining the position information of the point on the screen instructed by the user by the on-screen point indicating device 1125 from the screen display adapter and displaying this and “Yes” and “No”. Area 1510,15
This is done by comparing with 11 places on the screen.

Step 140 for confirming the reply contents
In 5, the user acknowledged the reply contents (YES)
In this case, send a reply to the client (step 5
13) is performed. If not acknowledged (NO), the reply information is erased (step 1406), and then the request information distribution request to the message accumulation and distribution software is made (step 505). When the reply information is deleted (step 1406), the server function call message 301 received in step 501 is received.
The content of the reply information 220 in the request reply table 1301 corresponding to is deleted.

FIG. 16 shows the function call request mediation mechanism 101 on the client side in the third embodiment.
The reply receiving unit (not shown in FIG.
(Corresponding to No. 4) is a flowchart showing a processing procedure executed. The flowchart shown in FIG. 16 is the first shown in FIG.
Immediately after step 603 (writing the reply information to the request reply table) of the processing procedure of the embodiment, step 1601 (notification to the user of reply information acquisition) is provided. The contents of step 1601 for notifying the user of acquisition of reply information are the request reception time 1302, the nickname of the call (symbol such as characters and figures) 1204, the server identifier 211 and the function identifier 2.
12 and the argument sequence 213 and the return value sequence 221 are displayed on the screen. Here, the server identifier 211 and the function identifier 212 are the server identifier 211 included in the server reply message 401 received in step 601.
And the function identifier 212. Further, the request reception time 1302, the argument arrangement 213, and the return value arrangement 221 are
Among the plurality of columns provided in the request reply table 1301, the server reply message 401 (see FIG.
(See) column. A nickname for calling (a symbol such as a character or a figure) 1204 is a column corresponding to the server reply message 401 among a plurality of columns provided in the auxiliary information table 1102.

FIG. 17 is a diagram showing a display example requested by the auxiliary information table management program 1121 to the screen display adapter 1123 in step 1601 of notifying the user of acquisition of reply information. As shown in FIG. 17, in columns 1701 to 1708, request acceptance date / time 1302, nickname of call (symbol such as characters and figures) 1204, server identifier 211, and function identifier 212.
An argument list 213 and a return value list 221 are displayed respectively.

FIG. 18 is a flow chart showing the process flow of the auxiliary information table management program 1121 shown in FIG. As shown in FIG. 18, in the auxiliary information table management program 1121, the screen display management adapter 11
23 is requested to display an input screen (step 1801), then input processing from the user's keyboard (step 1802) is performed, the input contents are written to the auxiliary table (step 1803), and the processing ends. .

FIG. 19 shows the screen display management adapter 1 in step 1801 of the input screen display request shown in FIG.
FIG. 13 is a diagram showing an example of display contents for which a display request to 123 is made.
In the figure, areas 1901 to 1907 surrounded by dotted lines are a server identifier 211, a function identifier 212, a nickname of a call (a symbol such as a character or a figure) 1204, a reply information valid period 1203, and a failure reply pattern 1202.
Is an area for receiving user input, and is blank in the initial display state.

In the input processing step 1802 from the user's keyboard shown in FIG. 18, for example, the instruction of the area to be inputted is accepted by the on-screen point indicating device 1125, and the input information from the keyboard 1122 is accepted to thereby obtain the server identifier. 211, a function identifier 212, a nickname for calling (a symbol such as a character or a figure) 1204, a reply information valid period 1203, and a failure reply pattern 1
A process of accepting user input information regarding 202 is performed.

In the step 1803 of writing the input contents to the auxiliary table shown in FIG. 18, the auxiliary information table 11
02, a field is added, and further, the server identifier 2 obtained in the input processing step 1802 from the keyboard 1122
11, a function identifier 212, a nickname for calling (a symbol such as a character or a figure) 1204, and a reply information valid period 120
3 and the information regarding the failure reply pattern 1202 are written in the added column.

According to the above-described third embodiment, the first
In addition, by providing the means for the user to know the reply information acquisition, it becomes easy for the user to know when to start the client program. Secondly, by providing the means for confirming the reply content at the time of reply transmission, it is possible to reduce the possibility that the client program receives the unjust reply and performs the unjust process. Thirdly, by providing the automatic management means for the expiration date of the reply information, it is possible to avoid the situation where the client program receives old information whose expiration date has passed. Fourthly, by providing the means for setting the failure reply pattern, it is possible to set an appropriate reply pattern to be sent to the client program at the time of notifying the call failure to the client program, and to smoothly cooperate with the client program. It will be possible. Fifth, by providing a means for giving a nickname (a symbol such as a character or a figure) to the server function call, it is displayed on the screen when notifying the user of acquisition of reply information or when reply contents are sent when reply is sent. The server function call nickname (characters, figures, etc.) can be added to the message, and the user can easily understand the message content.

[0094]

According to the present invention, it is possible to asynchronously call the server function by the client computer without changing the client program and the server program developed on the premise of the synchronous call.

That is, according to the first, second, third, and seventh client-server type system function asynchronous invocation methods, the client program transmits the server function synchronous invocation message, and the server function synchronous invocation message is transmitted. When accepted, the contents of the function synchronization call message and the contents of the server reply message which is the response from the server computer corresponding to the function synchronization call message are judged to be stored in the table (request reply table), and the client program The server reply message is edited and transmitted as information including the success or failure of the function call. The process of receiving the server function synchronization call message from the client program and the process of transmitting the server reply message to the client program are performed in synchronization.

However, the transmission of the server function synchronous call message to the server computer and the transmission of the server reply message from the server computer are performed asynchronously.

As a result, the client computer can call the server function asynchronously without changing the client program and the server program developed on the premise of synchronous calling.

According to the fourth method for asynchronously calling the function of the client-server type system, whether the server reply message is valid at the current time is determined by the validity period of the server function call preset by the user. It becomes possible to inspect, and it is possible to prevent the client program from receiving an old server reply message that has expired.

According to the fifth method for asynchronously calling the function of the client-server type system, a part of the contents of the server reply message is presented to the user before the server reply message is transmitted to the client program. Since it becomes possible to accept an input regarding acceptance or rejection of the server reply message by the user, it is possible to reduce the possibility that the client program receives the unjust server reply message and performs the unjust process. Further, according to the fifth function asynchronous invocation method of the client-server type system, when the server reply message obtained by the asynchronous server function invocation is received in the processing by the function invocation request mediation mechanism,
Since a part of the content is presented to the user in advance, the user can start the client program at an appropriate time.

Further, according to the sixth method for asynchronously calling the function of the client-server type system, when presenting a server reply message or a part of its contents to the user, the symbols such as the above character strings and figures are simultaneously displayed. The user can easily understand the content of the server reply message because the symbol such as the character string or the graphic is presented instead of presenting or presenting the server reply message or a part of the contents thereof.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration example (first embodiment) of a client-server type system to which a method for asynchronously calling a function of a client-server type system of the present invention is applied.

FIG. 2 is an explanatory diagram showing an example of a server function call message 301 used in the client-server type system shown in FIG.

3 is an explanatory diagram showing an example of a server reply message 401 used in the client-server type system shown in FIG.

4 is an explanatory diagram showing details of a function call request mediation mechanism 101a and a request reply table 102 on the client side shown in FIG.

FIG. 5 is a flowchart showing a processing procedure in a function call request mediation mechanism 101a on the client side.

FIG. 6 is a flowchart showing a processing procedure in a reply receiving unit 204 from a server existing in the function call request mediation mechanism 101a on the client side.

FIG. 7 is a flowchart showing a processing procedure in a function call request mediation mechanism 101b on the server side.

FIG. 8 is an explanatory diagram showing a procedure of asynchronous call according to the first embodiment.

FIG. 9 is a block diagram showing a configuration example (second embodiment) when the present invention is applied to a client-server type system having a naming function.

FIG. 10 is an explanatory diagram showing a configuration example of a name identifier table 903 provided on the computer 109e shown in FIG.

FIG. 1 is a block diagram showing a configuration example (third embodiment) of a client-server type system to which the function asynchronous invocation method for a client-server type system according to the present invention is applied.

12 is an auxiliary information table 1 shown in FIG.
FIG. 3 is an explanatory diagram showing details of the configuration of 102.

13 is an explanatory diagram showing a configuration example of a request reply table 1301 shown in FIG.

FIG. 14 is a flowchart showing processing executed in the function call request mediation mechanism 101a on the client side shown in FIG.

15 is an explanatory diagram showing a display example requested by the auxiliary information table management program 1121 to the screen display adapter 1123 in the reply content confirmation step 1405 shown in FIG.

FIG. 16 is a function call request mediation mechanism 101a on the client side in the third embodiment.
5 is a flowchart showing a processing procedure executed by a reply receiving unit of the server in the server.

FIG. 17 is a screen display adapter 1 in which the auxiliary information table management program 1121 is executed in step 1601 of notifying the user of acquisition of reply information shown in FIG.
It is explanatory drawing which shows the example of a display requested to 123.

FIG. 18 is a flowchart showing a processing procedure of an auxiliary information table management program 1121 shown in FIG. 11.

19 is a screen display management adapter 11 in step 1801 of the input screen display request shown in FIG.
It is a figure which shows an example of the display content which makes a display request to 23.

[Explanation of symbols]

100, 900, 1100 ... Client-server type system, 108 ... Network, 109a, 109b, 1
09c, 109d, 109e, 109f, 109g ... Computer, 105 ... Client program, 107 ... Server program, 101a, b ... Function call request mediation mechanism, 104a, b ... Message storage / delivery software, 102 ... Request reply table.

Claims (7)

[Claims] 1. At least one client computer and at least one server computer are connected to each other via a network, the client computer includes a client program for transmitting a server function call message to the server computer, and the server computer. Is a function asynchronous invocation method applied to a client-server system having a server program that receives a server function invocation message from a client computer and executes the contents instructed by the server function invocation message in a synchronous state. The client program in the first sends the server function call message described above.
And the first program receives the server function call message, stores the contents in a table, then asynchronously sends the server function call message to the network, and sends the server function call message from the server computer to the server function call message. When the server reply message is received asynchronously via the network, the two are stored in the above table in association with each other, and when the server function call message is received, the contents of the server function call message are referred to by referring to the table. When at least one of the server reply messages for the server function call message is not stored, the server reply message that indicates that the synchronous call to the server computer has failed for the client program A second step of transmitting the server reply message obtained from the table to the client program when the content of the server function call message and the server reply message for the server function call message are both stored. The second program asynchronously receives the server function call message via the network, transmits the received server function call message to the server program of the server computer, and further transmits the server reply message transmitted from the server computer. The third step of receiving and transmitting to the network asynchronously, and the client program of the client computer,
And a fourth step of receiving the server function call message, calling and executing the function specified by the server function call message, creating a server reply message, and transmitting the server reply message to the second program. A feature of a client-server system characterized by the asynchronous call method. 2. At least one client computer and at least one server computer are connected to each other via a network, and the client computer comprises a client program for transmitting a server function call message to the server computer in a synchronous state, and In the function asynchronous invocation method, the server computer receives a server function invocation message from a client computer and has a server program for executing the contents instructed by the server function invocation message in a synchronous state. The client program in the client computer transmits the server function call message to the first client program.
And the server function call message mediation mechanism provided in the client computer receives the server function call message, and the request reply table provided in the client computer stores the information included in the server function call message. If it is determined that the information is not already stored, and if it is determined that the information is not stored, then a server reply message indicating that the synchronous call to the server computer has failed is transmitted to the client program. And, the information included in the server function call message is stored in the request reply table, and the server function call message is transmitted, and when it is determined that the information is stored,
It is determined whether the server reply message corresponding to the server function call message from the server computer is stored in the field corresponding to the field in which the information included in the server function call message is stored. If it is determined that it is stored, the above server reply message is sent to the client program, and if it is determined that the server reply message is not stored, the client program is synchronized with the server computer. The second step of transmitting a server reply message containing the fact that the call failed, and the message storage and distribution software provided in the client computer are transmitted from the server function call message intermediary mechanism in the second step. Third step of receiving the server function call message that is received and asynchronously transmitting the received server function call message to the target server computer via the network; and message storage and distribution software provided in the server computer. Receives the server function call message transmitted from the message storage / delivery software in the client computer in the third step asynchronously,
The fourth step of transmitting to the server function call message intermediary mechanism provided in the server computer, and the server function call message intermediary mechanism provided in the server computer were provided in the server computer in the fourth step. Receives the server function call message sent from the message storage and distribution software,
The fifth step of transmitting to the server program provided in the server computer and the server program provided in the server computer are the fifth step.
Receiving the server function call message sent in step, calling and executing the function specified by the server function call message, creating a server reply message and sending it to the server function call message intermediary mechanism of the server computer. Step 6 and the server function call message intermediary mechanism provided in the server computer receive the server reply message sent from the server program in the sixth step and send it to the message storage / delivery software in the server computer. And the message storage / delivery software provided in the server computer receives the server reply message transmitted in the sixth step, and asynchronously transmits the server reply message to the target client computer via the network. A seventh step of transmitting the received server reply message, and the message storage / delivery software provided in the client computer, the server reply message transmitted from the message storage / delivery software in the server computer in the seventh step is transmitted to the network. The eighth step of asynchronously receiving via the server computer and transmitting to the server function call message intermediary mechanism provided in the client computer; and the server function call message intermediary mechanism provided in the client computer, The server reply message transmitted in step is received, and it corresponds to the column in the request reply table in the client computer in which the information about the server function call included in the server reply message is stored. Function asynchronous call method of a client-server system characterized by being comprised of a ninth step of storing the server reply message column. 3. A server function call message mediation mechanism provided in the client computer is configured as one of libraries to be linked at the time of compiling the client program, and when the client program sends a server server function call message, 3. The method for asynchronously calling a function of a client-server type system according to claim 2, wherein the main body of the client program selects the server function call message mediation mechanism in the library. 4. In the process of the server function call message mediation mechanism in the second step, the client computer associates information of the server function call message with a valid period of the server function call preset by the user. 4. The method according to claim 2 or 3, further comprising a step of determining whether or not the current time is within the valid period before attaching and holding the server reply message to the client program. Function of client-server type system described Asynchronous call method. 5. In the processing in the server function call message mediation mechanism in the second step, a part of the contents of the server reply message is presented to the user before the server reply message is transmitted to the client program. 5. The method for asynchronously calling a function of a client-server type system according to claim 2, 3, or 4, further comprising a step of receiving an input regarding acceptance or rejection of a server reply message by a user. 6. In the process by the server function call message mediation mechanism in the second step, the client computer holds a symbol such as a character string or a graphic for the server function call message preset by the user. , When presenting a server reply message or part of its contents to the user, present symbols such as the above character strings and figures at the same time,
Alternatively, instead of presenting the server reply message or presenting a part of the content thereof, a step of presenting the symbol such as the character string or the graphic is provided. A method for asynchronously calling the function of the client-server type system according to item 5. 7. At least one client computer and at least one server computer are connected to each other via a network, and the client computer has synchronous call request distribution software necessary for transmitting a server function call message to the server computer. A client program, and the server computer includes a synchronous call request distribution software and a server program required to receive a server function call message from the client computer and execute the contents instructed by the server function call message. A function applied to a provided client-server type system, which is an asynchronous invocation method, wherein the client computer is a client program in the client computer and a synchronous invocation request delivery. The first step of transmitting the server function call message to the network by the function of the software, and the first computer transmits the message in the first step by the function of the synchronous call request distribution software provided in the first computer. The received server function call message, and the received server function call message further includes a name identifier table provided in the first computer by the operation of the naming function program provided in the first computer. The server function call message intermediary mechanism provided in the second computer is searched for based on the call function name stored in the second computer, and the server function call message of the address is searched for by the function of the synchronous call request distribution software. In the second computer above Second transmission to the provided server function call message mediation mechanism via the network
And the second computer receives the server function call message transmitted in the second step from the network by the function of the synchronous call request distribution software provided in the second computer, The server function call message mediation mechanism determines whether or not the information included in the server function call message is already stored in the request reply table provided in the second computer, and the information is not stored. If it is determined that the client computer of the client computer has a server reply message indicating that the synchronous call to the server computer has failed, the operation of the synchronous call request distribution software provided in the second computer. By network Information stored in the server function call message is stored in the request reply table, and the server function call message is sent to the third computer by the action of the message storage / delivery software provided in the second computer. When it is determined that the information is stored,
It is determined whether the server reply message corresponding to the server function call message from the server computer is stored in the field corresponding to the field in which the information included in the server function call message is stored. If determined to be stored, the server reply message is transmitted to the client program of the client computer via the network by the operation of the synchronous call request distribution software provided in the second computer, If it is determined that the server reply message is not stored, the synchronous call request distribution software provided in the second computer causes the client program of the client computer to perform a synchronous call to the server computer. The third step of transmitting a server reply message having the content of the failed sending via the network, and the message storage and distribution software provided in the third computer is the second computer in the third step. The server function call message transmitted from the message storage / delivery software in the computer is asynchronously received via the network, and is transmitted to the server function call message intermediary mechanism provided in the third computer. A server function invocation message intermediary mechanism provided in the server receives the server function invocation message and transmits the server function invocation message to the network by the operation of the synchronous invocation request distribution software provided in the third computer. 4 steps and server calculation The synchronous call request distribution software provided in the machine receives the server function call message transmitted in the fourth step via the network, and the server program provided in the server computer is designated by the server function call message. Fifth step of calling and executing a function to create a server reply message and sending to the network via the server server's synchronous server function call message distribution software, and a synchronous call provided in the third computer The request distribution software receives the server reply message transmitted in the fifth step via the network, and the server function call message intermediary mechanism provided in the third computer causes the message in the third computer to operate. Accumulation The message storage and distribution software that is sent to the distribution software and is installed in the third computer is
A sixth step of receiving the server reply message and asynchronously transmitting it to the message storage / delivery software in the second computer via a network; and storing / delivering a message provided in the second computer. The software asynchronously receives the server reply message transmitted from the message storage / delivery software in the third computer in the sixth step, and by the function of the server function call message intermediary mechanism provided in the third computer. And a seventh step of storing the server reply message in a column corresponding to the column in the request reply table that stores the information about the server function call included in the server reply message. Client-server type system Function Asynchronous call method.