JP2006085365A - Proxy device, service use device, proxy program, service use program, recording medium and asynchronous operation provision method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide asynchronous operation to a client even if service supports synchronous operation and does not support the asynchronous operation. <P>SOLUTION: This proxy device has: a request reception means 41 receiving a request from a service use means; an asynchronous execution means 43 generated according to a use request of the asynchronous operation related to the service from the service use means 10, executing processing related to asynchronization; and a response holding/transmission means 42 transmitting a response to the service use means 10 according to the request from the service use means 10, temporarily holding a processing result of the synchronous operation executed by a service provision means 30 according to the use request of the asynchronous operation, and transmitting it to the service use means 10 as a processing result of the asynchronous operation. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a proxy device, a service using device, a proxy program, a service using program, a recording medium, and an asynchronous operation providing method.

  Traditionally, there are services that only support synchronous operations. An example of a service that supports only synchronous operation, for example, is shown in FIG. FIG. 1 is a diagram illustrating an example of a service that supports only synchronous operation.

  As shown in FIG. 1, a user uses a client service (hereinafter simply referred to as a client) installed in a personal computer (hereinafter simply referred to as a PC) or the like to obtain scanned scan data as a scan service. Even if requested, for example, if the scan service implemented in the image forming apparatus supports only synchronous operation, if a large amount of documents are scanned, scan data is acquired until all scans are completed. There was a problem that the response to the request was not returned to the client.

  Therefore, for example, even if the client tries to display the scan data on the display of the PC, the response to the scan data acquisition request is not returned from the scan service until all the scans are completed. There was a problem. In addition, the client and the scan service remain connected until all the scans are completed, so that there is a problem that the entire network is occupied during the scan.

  On the other hand, a service that also supports asynchronous operations solves the problems described above. An example of a service that also supports asynchronous operations is shown in FIG. Figure 2 shows an example of a service that also supports asynchronous operations.

  As shown in FIG. 2, when a user requests a scan service to acquire scanned scan data using a client mounted on a PC or the like, for example, the scan service mounted on the image forming apparatus or the like If the asynchronous operation is also supported, even if a large amount of documents are scanned, for example, only the scan data of the first page can be returned to the client as a response to the scan data acquisition request for the time being.

  Therefore, for example, when the client tries to display the scan data on the display of the PC, for the time being, only the scan data of the first page can be quickly displayed. In addition, since the client can asynchronously acquire the scan data of the remaining pages from the scan service, the global area of the network is not occupied during the scan.

  However, for example, when a device or the like on which a service that supports only the synchronous operation as described above is already shipped and a system or the like including the device is constructed, as shown in FIG. There was a problem that asynchronous operations could not be provided to clients.

  The present invention has been made in view of the above points, and an object thereof is to enable an asynchronous operation to be provided to a client even in a service that supports a synchronous operation and does not support an asynchronous operation.

  In the following, examples of general synchronous operation and asynchronous operation are shown in FIGS. FIG. 3 is a diagram illustrating an example of a general synchronization operation.

  As shown in FIG. 3, for example, the client transmits a GetDocList request that calls a GetDocList operation that is a synchronous operation for acquiring a list of documents to a service that supports only the synchronous operation, for example, a document service (sequence SQ1). Hereinafter, the service is also simply referred to as a server.

  When the server receives a GetDocList request from the client, the server executes a document list acquisition process (GetDocList operation). When the server acquires a document list, the server sends a GetDocListResponse, which is a return value of the GetDocList operation, to the requesting client ( Sequence SQ2).

  It should be noted that the client cannot execute other processes from when a request is transmitted until a response is received.

  Hereinafter, a general asynchronous operation is shown in FIG. 4 by taking the case of polling as an example. FIG. 4 is a diagram illustrating an example of a general asynchronous operation (polling).

  As shown in FIG. 4, for example, the client transmits a GetDocList request that calls a GetDocList operation that is an asynchronous operation for acquiring a list of documents to a server that supports the asynchronous operation (sequence SQ10).

  When the server receives the GetDocList request from the client, the server returns Acknowledgment (hereinafter simply referred to as Ack) to the client (sequence SQ11), and executes document list acquisition processing (GetDocList operation).

  When the client sends a request, it immediately receives an Ack from the server and can execute another process.

  Further, after a while, the client transmits an IsCompleted request for calling an IsCompleted operation for confirming whether or not the GetDocList operation has ended (sequence SQ12).

  When the server receives the IsCompleted request from the client and determines that the GetDocList operation has not ended yet, the server transmits a response including No indicating that the operation has not ended to the requesting client (sequence). SQ13).

  Further, after a while, the client transmits an IsCompleted request for calling an IsCompleted operation for confirming whether or not the GetDocList operation has ended (sequence SQ14).

  When the server determines that the GetDocList operation has already ended when it receives the IsCompleted request from the client, it sends a response including Yes indicating that the operation has ended to the requesting client (sequence SQ15). .

  When the client receives a response including Yes indicating that the operation is completed from the server, the client transmits a GetResult request for calling the GetResult operation for obtaining the result of the GetDocList operation to the server (sequence SQ16).

  When the server receives a GetResult request from the client, the server executes a result acquisition process (GetResult operation). When the server acquires the result of the GetDocList operation, the server sends a GetDocListResponse which is a return value of the GetResult operation to the requesting client (sequence). SQ17).

  As shown in FIG. 4, when the server supports asynchronous operations, the client can immediately obtain a response corresponding to the request from the server and execute other processes during the document acquisition process. .

  Hereinafter, a general asynchronous operation is shown in FIG. FIG. 5 is a diagram illustrating an example of a general asynchronous operation (coldback).

  As shown in FIG. 5, for example, the client transmits a GetDocList request that calls a GetDocList operation that is an asynchronous operation for acquiring a list of documents to a server that also supports the asynchronous operation (sequence SQ20).

  When the server receives a GetDocList request from the client, the server returns Ack to the client (sequence SQ21), and executes document list acquisition processing (GetDocList operation).

  When the client sends a request, it immediately receives an Ack from the server and can execute another process.

  When the document list acquisition process (GetDocList operation) ends, the server transmits GetDocListResponse, which is the return value of the GetDocList operation, to the requesting client (sequence SQ22).

  When the client receives DocListResponse from the server, the client returns Ack to the server (sequence SQ23).

  As shown in FIG. 5, when the server supports asynchronous operations, the client can immediately obtain a response corresponding to the request from the server and execute other processes during the document acquisition process. .

  Therefore, in order to solve the above-described problem, the present invention provides a service utilization unit that supports a service provided by a service providing unit that supports a synchronous operation related to a service and does not support an asynchronous operation related to a service. A proxy device capable of providing an asynchronous operation related to a service, in response to a request receiving means for receiving a request from the service using means and a request for using the asynchronous operation related to the service from the service using means Asynchronous execution means for executing processing related to asynchronous generation, and sending a response to the service use means in response to a request from the service use means, while providing the service in response to a use request for the asynchronous operation Means Temporarily holds a processing result of the synchronization operations described row, as the result of processing asynchronous operations, and having a a response holding and transmitting means for transmitting to said service means.

  According to the present invention, the asynchronous operation related to the service is provided to the service using means that supports the service provided by the service providing means that supports the synchronous operation related to the service and does not support the asynchronous operation related to the service. A proxy device that enables processing, a request receiving unit that receives a request from the service using unit, and a process that is generated in response to a use request for an asynchronous operation related to the service from the service using unit and that is asynchronous An asynchronous execution means for executing the response and a synchronous operation executed by the service providing means in response to a request for use of the asynchronous operation while transmitting a response to the service use means in response to a request from the service use means Even if a service does not support asynchronous operations by temporarily holding processing results and having response holding / sending means to send to the service using means as processing results of asynchronous operations. Asynchronous operations can be provided to the client.

  Further, the present invention provides an asynchronous operation related to the service to a service using means that uses a service provided by a service providing means that supports a synchronous operation related to the service and does not support an asynchronous operation related to the service. A proxy device that enables processing, a request receiving unit that receives a request from the service using unit, and a process that is generated in response to a use request for an asynchronous operation related to the service from the service using unit and that is asynchronous An asynchronous execution means for executing the response and a synchronous operation executed by the service providing means in response to a request for use of the asynchronous operation while transmitting a response to the service use means in response to a request from the service use means The processing result, as the result of processing asynchronous operations, and having a a response transmitting means for transmitting to said service means.

  According to the present invention, the asynchronous operation related to the service is provided to the service using means that supports the service provided by the service providing means that supports the synchronous operation related to the service and does not support the asynchronous operation related to the service. A proxy device that enables processing, a request receiving unit that receives a request from the service using unit, and a process that is generated in response to a use request for an asynchronous operation related to the service from the service using unit and that is asynchronous An asynchronous execution means for executing the response and a synchronous operation executed by the service providing means in response to a request for use of the asynchronous operation while transmitting a response to the service use means in response to a request from the service use means A response sending means for sending a processing result as a processing result of an asynchronous operation to the service using means, thereby supporting a synchronous operation; even a service that does not support an asynchronous operation is asynchronous with respect to a client. Operation can be provided.

  Further, as means for solving the above problems, a service use device, a proxy program, a service use program, a recording medium, and an asynchronous operation providing method may be used.

  The request receiving means described in the claims corresponds to, for example, a request receiving unit 41 or a request receiving unit 51 described later. Further, the asynchronous execution means described in the claims corresponds to, for example, an asynchronous thread 43 or an asynchronous thread 53 described later. The response holding / transmitting means described in the claims corresponds to, for example, a response holding / transmitting unit 42 described later. Moreover, the response transmission means described in the claims corresponds to, for example, a response transmission unit 52 described later. The proxy management unit described in the claims corresponds to, for example, a service / proxy correspondence table 102 or an operation / proxy correspondence table 104 described later.

  According to the present invention, it is possible to provide an asynchronous operation to a client even for a service that supports a synchronous operation and does not support an asynchronous operation.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  First, FIG. 6 shows a hardware configuration of an example of the client device 1 in which the client 10 is installed. FIG. 6 is a hardware configuration diagram of an example of the client device.

  As illustrated in FIG. 6, the client device 1 includes an input device 11, a display device 12, a drive device 13, a ROM (Read Only Memory) 15, a RAM (Random Access Memory) 16, and a CPU (Central Processing). (Unit) 17, interface device 18, and HDD (Hard Disk Drive) 19.

  The input device 11 includes a keyboard and a mouse that are operated by a user of the client device 1, and is used to input various operation signals to the client device 1. The display device 12 includes a display used by the user of the client device 1 and displays various types of information. The interface device 18 is an interface that connects the client device 1 to a network or the like.

  A program (hereinafter referred to as a client program) or the like corresponding to the client (client service) 10 is provided to the client device 1 by a recording medium 14 such as a CD-ROM or downloaded through a network. The recording medium 14 is set in the drive device 13, and the client program is installed in the HDD 19 from the recording medium 14 via the drive device 13.

  The ROM 15 stores data and the like. The RAM 16 reads and stores a client program and the like from the HDD 19 when the client device 1 is activated. The CPU 17 executes processing according to a client program and the like read and stored in the RAM 16.

  The HDD 19 stores a client program, data, and the like.

  A hardware configuration of an example of the proxy apparatus 2 in which the proxy service (hereinafter simply referred to as a proxy) 20 is installed is shown in FIG. FIG. 7 is a hardware configuration diagram of an example of the proxy device.

  As shown in FIG. 7, the proxy device 2 includes a drive device 23, a ROM 25, a RAM 26, a CPU 27, an interface device 28, and an HDD 29.

  The interface device 28 is an interface that connects the proxy device 2 to a network or the like.

  A program corresponding to the proxy (proxy service) 20 (hereinafter referred to as a proxy program) or the like is provided to the proxy device 2 by a recording medium 24 such as a CD-ROM or downloaded through a network. The recording medium 24 is set in the drive device 23, and the proxy program is installed from the recording medium 24 to the HDD 29 via the drive device 23.

  The ROM 25 stores data and the like. The RAM 26 reads and stores a proxy program or the like from the HDD 29 when the proxy device 2 is activated. The CPU 27 executes processing in accordance with a proxy program or the like read and stored in the RAM 26.

  The HDD 29 stores a proxy program, data, and the like.

  Hereinafter, an exemplary hardware configuration of the server device 3 in which the server (service) 30 is installed is illustrated in FIG. FIG. 8 is a hardware configuration diagram of an example of the server apparatus. It is assumed that the server 30 shown below supports synchronous operation and does not support asynchronous operation.

  As shown in FIG. 8, the server device 3 includes a drive device 33, a ROM 35, a RAM 36, a CPU 37, an interface device 38, and an HDD 39.

  The interface device 38 is an interface that connects the server device 3 to a network or the like.

  A program corresponding to the server 30 (hereinafter referred to as a server program) or the like is provided to the server device 3 by a recording medium 34 such as a CD-ROM or downloaded through a network. The recording medium 34 is set in the drive device 33, and the server program is installed from the recording medium 34 to the HDD 39 via the drive device 33.

  The ROM 35 stores data and the like. The RAM 36 reads and stores a server program and the like from the HDD 39 when the server device 3 is activated. The CPU 37 executes processing according to a server program or the like read and stored in the RAM 36.

The HDD 39 stores a server program, data, and the like. When the server device 3 is an image forming device or the like, in addition to the hardware configuration shown in FIG. 8, a display / input device such as an operation panel, a reading device that executes scanning, a printing device that executes printing, or the like Is included.
(Polling)
Hereinafter, an example of the functional configuration of the proxy 20 in the case of polling is shown in FIG. FIG. 9 is a functional configuration diagram (part 1) of the proxy.

  As illustrated in FIG. 9, the proxy 20 includes a request reception unit 41, a response holding / transmission unit 42, an asynchronous thread 43, and a synchronous message transmission / reception unit 44.

  The request receiving unit 41 is a receiving unit that receives a request related to a synchronous operation or an asynchronous operation from the client 10. Further, when receiving a request for starting an asynchronous operation from the client 10, the request reception unit 41 generates an asynchronous thread 43.

  In response to a request from the client 10, the response holding / transmitting unit 42 transmits Ack or the like to the requesting client, while temporarily holding the execution result of the asynchronous operation executed by the server 30. In response to the request, it is transmitted to the requesting client 10 as the execution result of the synchronous operation.

  The asynchronous thread 43 is a thread that executes a process related to an asynchronous operation, and executes the synchronous message transmission / reception unit 44.

  The synchronization message transmission / reception unit 44 is a transmission / reception unit 44 that transmits / receives a synchronization message to / from the server 30.

  The asynchronous operation providing process via the proxy 20 is shown in FIG. 10 as an example of polling. FIG. 10 is a sequence diagram illustrating an asynchronous operation providing process via a proxy as an example of polling.

  As illustrated in FIG. 10, the client 10 transmits, for example, a GetDocListAsync request that calls a GetDocListAsync operation, which is an asynchronous operation for acquiring a list of documents, to the proxy 20 (sequence SQ30). Hereinafter, a request or response including the character string “Async” represents an asynchronous message unless otherwise specified.

  When the proxy 20 receives the GetDocListAsync request from the client 10, the proxy 20 returns Ack to the client 10 (sequence SQ31), and transmits a GetDocList request for calling the GetDocList operation that is a synchronous operation to the server 30 (sequence SQ32).

  The proxy 20 receives a request for using an asynchronous operation from the client 10, and exchanges an asynchronous message with the client 30 while exchanging a synchronous message with the server 30, as will be described later.

  When the client 10 transmits a request, it immediately receives Ack from the proxy 20 and can execute other processing.

  Upon receiving a GetDocList request from the proxy 20, the server 30 executes document list acquisition processing (GetDocList operation).

  Further, after a while, the client 10 transmits an IsCompleted request for calling an IsCompleted operation for confirming whether the GetDocList operation has ended to the proxy 20 (sequence SQ33).

  When the proxy 20 receives an IsCompleted request from the client 10 and determines that the GetDocList operation has not ended yet, the proxy 20 sends a response including No indicating that the GetDocList operation has not ended to the requesting client 10. Transmit (sequence SQ34).

  The proxy 20 determines whether or not the GetDocList operation has ended based on whether or not the GetDocListResponse including the list of documents, which is a return value of the GetDocList operation, has been received from the server 30.

  Here, for example, the proxy 20 receives GetDocListResponse from the server 30.

  On the other hand, the client 10 also transmits an IsCompleted request for calling an IsCompleted operation for confirming whether or not the GetDocList operation has ended to the proxy 20 (sequence SQ36).

  If the proxy 20 has received GetDocListResponse from the server 30, the proxy 20 determines that the GetDocList operation has ended, and transmits a response including Yes indicating that the GetDocList operation has ended to the requesting client 10 (sequence SQ37). .

  When the client 10 receives a response including Yes indicating that the operation is completed from the proxy 20, the client 10 transmits a GetResult request for calling the GetResult operation, which is an asynchronous operation, to acquire the result of the GetDocList operation (sequence). SQ38).

  When the proxy 20 receives the GetResult request from the client 10, the proxy 20 transmits the asynchronous GetDocListAsyncResponse including the list of documents received and received from the server 30 in the sequence SQ35 to the requesting client 10 (sequence SQ39).

Even if the server 30 supports the synchronous operation and does not support the asynchronous operation, the proxy 20 has the configuration shown in FIG. 9 and, as shown in FIG. Asynchronous messages are exchanged between them, and the proxy 20 and the server 30 exchange synchronous messages, so that the proxy 20 and / or the server 30 can provide an asynchronous operation to the client 10.
(Callback)
Hereinafter, an example of the functional configuration of the proxy 20 in the case of callback is shown in FIG. FIG. 11 is a functional configuration diagram (part 2) of the proxy.

  As illustrated in FIG. 11, the proxy 20 includes a request reception unit 51, a response transmission unit 52, an asynchronous thread 53, and a synchronous message transmission / reception unit 54.

  The request receiving unit 51 is a receiving unit that receives a request related to a synchronous operation or an asynchronous operation from the client 10. Further, when receiving a request for starting an asynchronous operation from the client 10, the request reception unit 51 generates an asynchronous thread 53.

  The response transmission unit 52 transmits Ack or the like to the requesting client in response to a request from the client 10, while transmitting the execution result of the asynchronous operation executed by the server 30 to the client 10 as the execution result of the synchronous operation. .

  The asynchronous thread 53 is a thread that executes a process related to an asynchronous operation, and executes the synchronous message transmission / reception unit 44.

  The synchronization message transmission / reception unit 44 is a transmission / reception unit 44 that transmits / receives a synchronization message to / from the server 30.

  The asynchronous operation providing process through the proxy 20 is shown in FIG. 12 as an example of callback. FIG. 12 is a sequence diagram illustrating an asynchronous operation providing process via a proxy as an example of a callback.

  As illustrated in FIG. 12, the client 10 transmits, for example, a GetDocListAsync request that calls a GetDocListAsync operation, which is an asynchronous operation for acquiring a list of documents, to the proxy 20 (sequence SQ40). The proxy 20 receives a request for using an asynchronous operation from the client 10, and exchanges an asynchronous message with the client 30 while exchanging a synchronous message with the server 30, as will be described later.

  When the proxy 20 receives the GetDocListAsync request from the client 10, the proxy 20 returns Ack to the client 10 (sequence SQ41), and transmits a GetDocList request for calling the GetDocList operation that is a synchronous operation to the server 30 (sequence SQ42).

  When the client 10 transmits the request, it immediately receives Ack from the server 30 and can execute other processing.

  Upon receiving a GetDocList request from the proxy 20, the server 30 executes document list acquisition processing (GetDocList operation). When the GetDocList operation is completed, the server 30 transmits a GetDocListResponse including a list of documents, which is a return value of the GetDocList operation, to the requesting proxy 20 (sequence SQ43).

  When proxy 20 receives GetDocListResponse from server 30, proxy 20 transmits GetDocListAsyncResponse including a list of documents to requesting client 10 (sequence SQ44).

  Upon receiving GetDocListAsyncResponse from proxy 20, client 10 returns Ack to server 30 (sequence SQ45).

  Even if the server 30 supports the synchronous operation and does not support the asynchronous operation, the proxy 20 takes the configuration shown in FIG. 11 and, as shown in FIG. Asynchronous messages are exchanged between them, and the proxy 20 and the server 30 exchange synchronous messages, so that the proxy 20 and / or the server 30 can provide an asynchronous operation to the client 10.

Hereinafter, a method of using the proxy 20 and a method of specifying the proxy 20 by the client 10 will be described with reference to FIGS.
(WSDL (proxy address only)-all operations through proxy)
An example of the functional configuration of the asynchronous operation providing system is shown in FIG. FIG. 13 is a functional configuration diagram (part 1) of the asynchronous operation providing system.

  As illustrated in FIG. 13, the server 30 includes a Web Services Description Language (WSDL) file 100 of the server (service) 30 in which the address (identifier) of the proxy 20 is described.

  In FIG. 13, the proxy 20 is configured as shown in FIG. 11, but may be configured as shown in FIG. 9. The same applies to FIG. 16, FIG. 19, FIG. 23, FIG. 30, FIG.

  The client 10 acquires the address of the proxy 20 described in the WSDL file 100 of the server 30, exchanges messages with the proxy 20 based on the address, and uses all operations via the proxy 20. To do.

  An example in which the address of the proxy 20 is described in the WSDL file 100 is shown in FIG. FIG. 14 is a diagram (part 1) illustrating an example in which a proxy address is described in a WSDL file.

As shown in FIG. 14, the proxy address 140 is described in the WSDL file 100.
(WSDL (service address)-all operations via proxy)
The concept of an example in which the client 10 informs the server 30 of the address (identifier) of the proxy 20 and uses the operation via the proxy 20 is shown in FIG. FIG. 15 is a conceptual diagram of an example in which an operation is used via a proxy after the server is informed of the proxy address.

  As shown in FIG. 15, the client 10 searches for a server 30 that the client 10 wants to use, for example ((1) in FIG. 15).

  When the client 10 discovers the server 30 that it wants to use ((2) in FIG. 15), the client 10 determines the proxy 20 based on the address of the proxy 20 included in the information provided from the server 30 at the time of discovery. Then, the operation is used ((3) in FIG. 15).

  Hereinafter, another example of the functional configuration of the asynchronous operation providing system is shown in FIG. FIG. 16 is a functional configuration diagram (part 2) of the asynchronous operation providing system.

  As shown in FIG. 16, the server 30 has a WSDL file 100 of the server 30 as shown in FIG.

  Hereinafter, another example in which the address of the proxy 20 is described in the WSDL file 100 is shown in FIG. FIG. 17 is a second diagram illustrating an example in which the proxy address is described in the WSDL file.

  As shown in FIG. 17, the WSDL file 100 describes a port 170 that supports only synchronous operations and a port 171 that supports both synchronous and asynchronous operations.

  Also, the WSDL file 100 of FIG. 17 includes an input message and an output message as shown in 172 in the synchronous operation, and only an input message is shown in the asynchronous operation as shown in 173. However, as shown at 174, only the output message is described in the return of the asynchronous operation.

  In the WSDL file 100 of FIG. 17, as shown in 175, two ports are prepared for one service (server), and the address of the proxy 20 is described in a port that supports asynchronous operation. Has been.

  When the client 10 acquires the WSDL file 100 included in the server 30 and uses the synchronous operation and the asynchronous operation, the client 10 acquires the address of the proxy 20 described in the port that supports the synchronous operation and the asynchronous operation. Based on the above, messages are exchanged with the proxy 20, and all operations are used via the proxy 20.

  Hereinafter, the processing using the operation is shown in FIG. FIG. 18 is a sequence diagram (part 1) illustrating processing using an operation.

  As shown in FIG. 18, client 10 transmits a request to acquire WSDL file 100 to server 30 (sequence SQ50).

  When server 30 receives the WSDL file 100 acquisition request from client 10, server 30 transmits WSDL file 100 as shown in FIG. 17 to client 10 (sequence SQ51).

When the client 10 acquires the WSDL file 100 as shown in FIG. 17 from the server 30, when using the synchronous operation and the asynchronous operation, the address of the proxy 20 described in the port that supports the synchronous operation and the asynchronous operation. Is exchanged with the proxy 20 based on the address, and all operations are used via the proxy 20 (sequence SQ52).
(WS-Policy-all operations via proxy)
FIG. 19 shows another example of the functional configuration of the asynchronous operation providing system. FIG. 19 is a functional configuration diagram (part 3) of the asynchronous operation providing system.

  As shown in FIG. 19, the server 30 has a WS-Policy file 101 of the server 30 as shown in FIG. 20 described later.

  An example in which the address of the proxy 20 is described in the WS-Policy file 101 is shown in FIG. FIG. 20 is a diagram (part 1) illustrating an example in which the proxy address is described in the WS-Policy file.

  As illustrated in FIG. 20, an address of a service that supports only a synchronous operation is described in 200, and an address of a service (proxy 20) that supports a synchronous operation and an asynchronous operation is described in 201.

  The client 10 must use either the address described in 200 or the address described in 201. When the client 10 acquires the WS-Policy file 101 included in the server 30 and uses the synchronous operation and the asynchronous operation, the client 10 acquires the address described in 201, and based on the address, the proxy 20 and the message Exchanges and uses all operations via the proxy 20.

  FIG. 21 shows processing using the operation. FIG. 21 is a sequence diagram (part 2) illustrating processing using an operation.

  As shown in FIG. 21, client 10 transmits an acquisition request for WS-Policy file 101 to server 30 (sequence SQ60).

  When server 30 receives the acquisition request for WS-Policy file 101 from client 10, server 30 transmits WS-Policy file 101 as shown in FIG. 20 to client 10 (sequence SQ61).

  When the client 10 acquires the WS-Policy file 101 as shown in FIG. 20 from the server 30, when using the synchronous operation and the asynchronous operation, the client 10 selects and acquires the address described in 201 of FIG. Based on the address, the proxy 20 transmits a getDocListAsync request that calls a getDocListAsync operation that is an asynchronous operation (sequence SQ62).

  When the proxy 20 receives the getDocListAsync request from the client 10, the proxy 20 returns Ack to the client 10 (sequence SQ63), and transmits a getDocList request for calling the getDocList operation that is a synchronous operation to the server 30 (sequence SQ64).

  When the server 30 receives a getDocList request from the proxy 20, the server 30 executes document list acquisition processing (getDocList operation). When the getDocList operation is completed, the server 30 transmits, for example, a getDocListResponse including a list of documents, which is a return value of the getDocList operation, to the requesting proxy 20 (sequence SQ65).

  When proxy 20 receives getDocListResponse from server 30, proxy 20 transmits, for example, getDocListAsyncResponse including a list of documents to requesting client 10 (sequence SQ66).

  In addition, client 10 transmits a getCapability request for calling getCapability operation, which is a synchronization operation, to proxy 20 (sequence SQ67).

  When the proxy 20 receives a getCapability request for calling a getCapability operation that is a synchronous operation from the client 10, the proxy 20 transmits the request to the server 30 (sequence SQ68).

  When the server 30 receives a getCapability request from the proxy 20, the server 30 executes a capability acquisition process (getCapability operation) of the server 30. When the getCapability operation ends, server 30 transmits getCapabilityResponse including the capability information of server 30 that is a return value of the getCapability operation to requesting proxy 20 (sequence SQ69).

When proxy 20 receives getCapabilityResponse from server 30, proxy 20 transmits the getCapabilityResponse to requesting client 10 (sequence SQ70).
(Service / proxy table-all operations via proxy)
Hereinafter, an example in which the client 10 searches for the server 30 and discovers the server 30, and then uses the operation via the proxy 20 based on the correspondence table between the service (server) and the proxy that the client 10 has. The concept is shown in FIG.

  FIG. 22 shows a concept of an example in which a client searches for a server and discovers the server, and then uses an operation via the proxy based on a correspondence table between the service (server) and the proxy that the client has. FIG.

  As shown in FIG. 22, the client 10 searches for a server 30 that the client 10 wants to use, for example ((1) in FIG. 22).

  When the client 10 finds a server (service) 30 that it wants to use ((2) in FIG. 22), a correspondence table (service / proxy correspondence table) between a server (service) and a proxy as shown in FIG. 102), the address of the server 30 discovered in (2) of FIG. 22 is passed to the corresponding proxy (for example, proxy 20), and asynchronous operation and synchronous operation are used ((3) of FIG. 22).

  Hereinafter, another example of the functional configuration of the asynchronous operation providing system is shown in FIG. FIG. 23 is a functional configuration diagram (part 4) of the asynchronous operation providing system.

  As shown in FIG. 23, the client 10 has a service / proxy correspondence table 102 as shown in FIG. 24 to be described later, which associates a server (service) with a proxy.

  An example of the service / proxy correspondence table 102 is shown in FIG. FIG. 24 shows a service / proxy correspondence table.

  As shown in FIG. 24, the service / proxy correspondence table 102 includes a service (server) type and a proxy address as items.

  Hereinafter, based on the service / proxy correspondence table 102 as shown in FIG. 24, the client 10 that has acquired the proxy address corresponding to the server to be used designates the server (target service) to be used for the proxy 20. Will be described with reference to FIGS.

  An example of target service designation processing is shown in FIG. FIG. 25 is a sequence diagram (part 1) illustrating target service designation processing.

  As shown in FIG. 25, the client 10 calls an operation for designating a target service prepared in the proxy 20 as shown in FIG. 26 described later (sequence SQ80).

  When the proxy 20 is called by the client 10 to specify a target service, it returns Ack to the client 10 (sequence SQ81), while setting the target service.

  The client 10 that has received Ack from the proxy 20 uses the asynchronous operation and the synchronous operation related to the designated service (server) through the proxy 20 (sequence SQ82).

  An example of an operation for specifying the target service is shown in FIG. FIG. 26 is a diagram illustrating an example of an operation for specifying a target service.

  As shown in FIG. 26, 260 describes an operation for designating a target service, and 261 describes an address of the target service.

  FIG. 27 shows another example of target service designation processing. FIG. 27 is a sequence diagram (part 2) of the target service designation process.

  As shown in FIG. 25, when using the asynchronous operation and the synchronous operation, the client 10 includes the target service in the SOAP header and transmits it to the proxy 20 as shown in FIG. SQ90).

  The proxy 20 that has received the server (service) use request as shown in FIG. 28 connects to the server 30 in accordance with the address of the target service included in the SOAP header (sequence SQ91).

  An example of describing the target service in the SOAP header is shown in FIG. FIG. 28 is a diagram illustrating an example in which the target service is described in the SOAP header.

As shown in FIG. 28, 280 describes the address of the target service, and 281 describes the operation name of the asynchronous operation.
(Some operations via proxy)
Hereinafter, an example in which the synchronous operation is used by directly communicating with the server 30 and the asynchronous operation is used via the proxy 20 is shown in FIG. FIG. 29 is a conceptual diagram illustrating an example in which the synchronous operation is used by directly communicating with the server, and the asynchronous operation is used via a proxy.

  As shown in FIG. 29, for example, the client 10 searches for a server 30 to be used ((1) in FIG. 29).

When the client 10 finds the server (service) 30 that it wants to use ((2) in FIG. 29), when using the synchronous operation, it communicates with the server 30 directly and uses it ((3) in FIG. 29). When the asynchronous operation is used, it is used via the proxy 20 ((4) in FIG. 29).
(WSDL-some operations via proxy)
FIG. 30 shows another example of the functional configuration of the asynchronous operation providing system. FIG. 30 is a functional configuration diagram (part 5) of the asynchronous operation providing system.

  As shown in FIG. 30, the server 30 includes a WSDL file 100 and a service interface 103 as shown in FIG.

  The service interface 103 represents an interface between the client 10 and the proxy 20 and the server 30.

  Another example in which the address of the proxy 20 is described in the WSDL file 100 is shown in FIG. FIG. 31 is a third diagram illustrating an example in which a proxy address is described in a WSDL file.

As shown in FIG. 31, 310 describes a proxy address. When the client 10 acquires the WSDL file 100 of the server 30 and uses an asynchronous operation, the client 10 acquires the address of the proxy indicated by 310, exchanges messages with the proxy 20 based on the address, and performs asynchronous processing. The operation is used via the proxy 20.
(WS-Policy-some operations via proxy)
FIG. 32 shows another example of the functional configuration of the asynchronous operation providing system. FIG. 32 is a functional configuration diagram (part 6) of the asynchronous operation providing system.

As shown in FIG. 32, the server 30 includes a WS-Policy file 101 and a service interface 103 as shown in FIG.
(WS-Policy (per operation)-some operations via proxy)
Another example in which the address of the proxy 20 is described in the WS-Policy file 101 is shown in FIG. FIG. 33 is a second diagram illustrating an example in which the proxy address is described in the WS-Policy file.

  As shown in FIG. 33, the WS-Policy file 101 describes the address of the proxy 20 or the server as a policy for each operation. The address 330 of the server is described in the location of the synchronous operation, and the address 331 of the proxy (for example, the proxy 20) is described in the location of the asynchronous operation.

  In the following, another example of processing using operations is shown in FIG. FIG. 34 is a sequence diagram (part 3) illustrating the process using the operation.

  As shown in FIG. 34, client 10 transmits an acquisition request for WS-Policy file 101 to server 30 (sequence SQ100).

  When server 30 receives the WS-Policy file 101 acquisition request from client 10, server 30 transmits WS-Policy file 101 as shown in FIG. 33 to client 10 (sequence SQ101).

  When the client 10 acquires the WS-Policy file 101 as shown in FIG. 33 from the server 30, when using the asynchronous operation, the client 10 selects and acquires the address described in 331 in FIG. Based on this, a getDocListAsync request for calling a getDocListAsync operation that is an asynchronous operation is transmitted to proxy 20 (sequence SQ102).

  When the proxy 20 receives the getDocListAsync request from the client 10, the proxy 20 returns Ack to the client 10 (sequence SQ103), while transmitting a getDocList request that calls the getDocList operation that is a synchronous operation to the server 30 (sequence SQ104).

  When the server 30 receives a getDocList request from the proxy 20, the server 30 executes document list acquisition processing (getDocList operation). When the getDocList operation is completed, the server 30 transmits, for example, a getDocListResponse including a list of documents, which is a return value of the getDocList operation, to the requesting proxy 20 (sequence SQ105).

  When proxy 20 receives getDocListResponse from server 30, proxy 20 transmits, for example, getDocListAsyncResponse including a list of documents to requesting client 10 (sequence SQ106).

  Further, when using the synchronous operation, the client 10 selects and acquires the address described in 330 of FIG. 33 and, based on the address, calls the getCapability operation that is a synchronous operation to the server 30. The request is transmitted (sequence SQ107).

When the server 30 receives a getCapability request from the client 10, the server 30 executes a capability acquisition process (getCapability operation) of the server 30. When the getCapability operation ends, the server 30 transmits a getCapabilityResponse including the capability information of the server 30 that is a return value of the getCapability operation to the requesting client 10 (sequence SQ108).
(WS-Policy (per server)-some operations via proxy)
Hereinafter, another example in which the address of the proxy 20 is described in the WS-Policy file 101 is shown in FIG. FIG. 35 is a diagram (No. 3) illustrating an example in which the proxy address is described in the WS-Policy file.

  As shown in FIG. 35, the WS-Policy file 101 describes the proxy 20 or server address as a policy for each server (service). The address 340 of the server is described in the location of the synchronous operation, and the address 341 of the proxy (for example, the proxy 20) is described in the location of the asynchronous operation.

  In the following, another example of processing using operations is shown in FIG. FIG. 36 is a sequence diagram (part 4) illustrating processing using an operation.

  As shown in FIG. 36, client 10 transmits an acquisition request for WS-Policy file 101 to server 30 (sequence SQ110).

  When server 30 receives the WS-Policy file 101 acquisition request from client 10, server 30 transmits WS-Policy file 101 as shown in FIG. 35 to client 10 (sequence SQ111).

  When the client 10 acquires the WS-Policy file 101 as shown in FIG. 36 from the server 30, when using the asynchronous service (server), the client 10 selects and acquires the address described in 341 of FIG. Based on the address, a getDocListAsync request that calls a getDocListAsync operation that is an asynchronous operation is transmitted to the proxy 20 (sequence SQ112).

  When the proxy 20 receives the getDocListAsync request from the client 10, the proxy 20 returns Ack to the client 10 (sequence SQ113), while transmitting a getDocList request for calling the getDocList operation that is a synchronous operation to the server 30 (sequence SQ114).

  When the server 30 receives a getDocList request from the proxy 20, the server 30 executes document list acquisition processing (getDocList operation). When the getDocList operation is completed, the server 30 transmits, for example, a getDocListResponse including a list of documents, which is a return value of the getDocList operation, to the requesting proxy 20 (sequence SQ115).

  When proxy 20 receives getDocListResponse from server 30, proxy 20 transmits, for example, getDocListAsyncResponse including a list of documents to requesting client 10 (sequence SQ116).

  Further, when using the synchronization service, the client 10 selects and acquires the address described in 340 in FIG. 36, and, based on the address, calls the getCapability operation that is a synchronization operation to the server 30. The request is transmitted (sequence SQ117).

When the server 30 receives a getCapability request from the client 10, the server 30 executes a capability acquisition process (getCapability operation) of the server 30. When the getCapability operation ends, server 30 transmits getCapabilityResponse including the capability information of server 30 as a return value of the getCapability operation to requesting client 10 (sequence SQ118).
(Operation proxy table-some operations via proxy)
Another example of the functional configuration of the asynchronous operation providing system is shown in FIG. FIG. 37 is a functional configuration diagram (part 7) of the asynchronous operation providing system.

  As shown in FIG. 37, the client 10 has an operation proxy correspondence table 104 as shown in FIG. 38, which will be described later, for associating operations with proxies. The server 30 also includes a service interface 103.

  An example of the operation proxy correspondence table 104 is shown in FIG. FIG. 38 is a diagram showing an operation proxy correspondence table.

  As shown in FIG. 38, the operation proxy correspondence table 104 includes an operation and a proxy address as items.

The client 10 acquires a proxy address corresponding to each operation based on the operation proxy correspondence table 104, connects to the proxy of the acquired address, and uses the operation via the proxy. As described above, there are two methods for passing the target service to the proxy.
(Large scan processing-all operations via proxy)
In the following, an example of a large amount of scan processing when all operations are routed through the proxy 20 is shown in FIG. FIG. 39 is a sequence diagram showing a large amount of scan processing when all operations are routed through a proxy.

  First, the client 10 transmits, for example, a startScan request for invoking a startScan operation, which is a synchronous operation, to the proxy 20 (sequence SQ120).

  When proxy 20 receives a startScan request from client 10, proxy 20 transmits the request to server 30 (sequence SQ121).

  When the server 30 receives the startScan request from the proxy 20, the server 30 starts scanning (executes the startScan operation), and when the scan is started, transmits a response including the return value of the startScan operation to the requesting proxy 20. (Sequence SQ122).

  When proxy 20 receives a response including a return value of the startScan operation from server 30, proxy 20 transmits the response to client 10 (sequence SQ123).

  When the client 10 receives a response including the return value of the startScan operation from the proxy 20, the client 10 transmits a getFirstPage request for invoking the getFirstPage operation, which is a synchronous operation for acquiring the first scanned page, to the proxy 20 (sequence SQ124). .

  When proxy 20 receives a getFirstPage request from client 10, proxy 20 transmits the request to server 30 (sequence SQ125).

  When the server 30 receives a getFirstPage request from the proxy 20, the server 30 acquires only the first page of data (executes the getFirstPage operation), and includes a response including the first page of data, which is a return value of the getFirstPage operation. Is transmitted to the requesting proxy 20 (sequence SQ126).

  When proxy 20 receives a response including a return value of the getFirstPage operation from server 30, proxy 20 transmits the response to client 10 (sequence SQ127).

  Since the client 10 acquires only the first page, the client 10 can acquire it quickly. For example, in response to a request from the user, only the acquired first page can be quickly displayed on the display or the like. .

  In addition, the client 10 transmits a getAllPagesAsync request for calling a getAllPagesAsync operation, which is an asynchronous operation for acquiring all remaining pages, to the proxy 20 (sequence SQ128).

  When the proxy 20 receives the getAllPagesAsync request from the client 10, the proxy 20 returns Ack to the client 10 (sequence SQ129), and transmits a getAllPages request for calling the getAllPages operation that is a synchronous operation to the server 30 (sequence SQ130).

  When the client 10 transmits the request, the client 10 immediately receives Ack from the proxy 20 so that other processing can be executed during the acquisition processing of all the remaining pages.

  When the server 30 receives a getAllPages request from the proxy 20, the server 30 executes an acquisition process (getAllPages operation) for all remaining pages. When the getAllPages operation is completed, the server 30 transmits a getAllPagesResults response including the data of all the remaining pages, which is a return value of the getAllPages operation, to the requesting proxy 20 (sequence SQ131).

  When the proxy 20 receives a getAllPagesResults response from the server 30, the proxy 20 transmits a getAllPagesAsyncResults response including data of all remaining pages to the requesting client 10 (sequence SQ132).

  Upon receiving the getAllPagesAsyncResults response from the proxy 20, the client 10 returns Ack to the proxy 20 (sequence SQ133).

By performing the processing as shown in FIG. 39, even in a large amount of scan processing, only the first page is acquired by a synchronous operation, and all subsequent pages are acquired by an asynchronous operation. Other processes can be executed in parallel with the scan process.
(Large scan processing-some operations via proxy)
Hereinafter, an example of a large amount of scan processing when asynchronous operation is used via the proxy 20 is shown in FIG. FIG. 40 is a sequence diagram showing a large amount of scan processing when the asynchronous operation is used via a proxy.

  First, the client 10 transmits a startScan request for invoking a startScan operation, which is a synchronous operation, to the server 30 (sequence SQ140).

  When the server 30 receives a startScan request from the client 10, the server 30 starts scanning (executes the startScan operation), and when the scan is started, transmits a response including a return value of the startScan operation to the requesting client 10. (Sequence SQ141).

  When the client 10 receives a response including the return value of the startScan operation from the server 30, the client 10 transmits to the server 30 a getFirstPage request that calls the getFirstPage operation, which is a synchronous operation for acquiring the first scanned page (sequence SQ142). .

  Upon receiving a getFirstPage request from the client 10, the server 30 acquires only the first page of data (executes the getFirstPage operation), and includes a response including the first page of data that is a return value of the getFirstPage operation. Is transmitted to the requesting client 10 (sequence SQ143).

  Since the client 10 acquires only the first page, the client 10 can acquire it quickly. For example, in response to a request from the user, only the acquired first page can be quickly displayed on the display or the like. .

  Further, when all the remaining pages are acquired, the client 10 transmits a getAllPagesAsync request for invoking a getAllPagesAsync operation that is an asynchronous operation to the proxy 20 (sequence SQ144).

  When the proxy 20 receives the getAllPagesAsync request from the client 10, the proxy 20 returns Ack to the client 10 (sequence SQ145), while transmitting a getAllPages request for calling the getAllPages operation that is a synchronous operation to the server 30 (sequence SQ146).

  When the client 10 transmits the request, the client 10 immediately receives Ack from the proxy 20 so that other processing can be executed during the acquisition processing of all the remaining pages.

  When the server 30 receives a getAllPages request from the proxy 20, the server 30 executes an acquisition process (getAllPages operation) for all remaining pages. When the getAllPages operation is completed, the server 30 transmits a getAllPagesResults response including the data of all the remaining pages, which is a return value of the getAllPages operation, to the proxy 20 of the request source (sequence SQ147).

  When the proxy 20 receives a getAllPagesResults response from the server 30, the proxy 20 transmits a getAllPagesAsyncResults response including data of all remaining pages to the requesting client 10 (sequence SQ148).

  Upon receiving the getAllPagesAsyncResults response from the proxy 20, the client 10 returns Ack to the proxy 20 (sequence SQ149).

By performing the processing as shown in FIG. 40, even in a large amount of scan processing, only the first page is acquired by a synchronous operation, and all subsequent pages are acquired by an asynchronous operation. Other processes can be executed in parallel with the scan process.
(Large document list acquisition processing-all operations via proxy)
FIG. 41 shows an example of a large amount of document list acquisition process when all operations are used via the proxy 20. FIG. 41 is a sequence diagram showing a large amount of document list acquisition process when all operations are used via a proxy.

  First, the client 10 transmits an execute Search request for calling an execute Search operation, which is a synchronous operation, to the server 30 (sequence SQ150).

  When proxy 20 receives the execute Search request from client 10, proxy 20 transmits the request to server 30 (sequence SQ151).

  Upon receiving an executeSearch request from the proxy 20, the server 30 starts searching for a list of documents (executes the executeSearch operation), and transmits a response including the return value of the executeSearch operation to the requesting proxy 20 (sequence). SQ152).

  When proxy 20 receives the response including the return value of executeSearch operation from server 30, proxy 20 transmits the response to client 10 (sequence SQ153).

  When the client 10 receives a response including the return value of the executeSearch operation from the proxy 20, for example, the client 10 sends a getTop10Page request to the proxy 20 that invokes a getTop10Page operation that is a synchronous operation for acquiring the top 10 data of the search result. Transmit (sequence SQ154).

  When proxy 20 receives a getTop10Page request from client 10, proxy 20 transmits the request to server 30 (sequence SQ155).

  When the server 30 receives a getTop10Page request from the proxy 20, the server 30 acquires data (list data) corresponding to the top 10 search results (executes the getTop10Page operation), and the top 10 that are return values of the getTop10Page operation. The response including the minute data is transmitted to the requesting proxy 20 (sequence SQ156).

  When proxy 20 receives a response including a return value of the getTop10Page operation from server 30, proxy 20 transmits the response to client 10 (sequence SQ157).

  Since the client 10 acquires only the top 10 data, it can be acquired quickly. For example, in response to a request from the user, only the acquired top 10 data can be quickly displayed on the display or the like. Can do.

  In addition, client 10 transmits a getAllAsync request for calling getAllAsync operation, which is an asynchronous operation for acquiring all remaining list data, to proxy 20 (sequence SQ158).

  When the proxy 20 receives the getAllAsync request from the client 10, it returns Ack to the client 10 (sequence SQ159), and transmits a getAll request for calling the getAll operation, which is a synchronous operation, to the server 30 (sequence SQ160).

  When the client 10 transmits the request, it immediately receives Ack from the proxy 20 so that other processing can be executed during the acquisition processing of all the remaining list data.

  When receiving a getAll request from the proxy 20, the server 30 executes acquisition processing (getAll operation) of all remaining lists. When the getAll operation is completed, the server 30 transmits a getAllResults response including all remaining list data, which is a return value of the getAll operation, to the requesting proxy 20 (sequence SQ161).

  When the proxy 20 receives a getAllResults response from the server 30, the proxy 20 transmits a getAllAsyncResults response including all remaining list data to the requesting client 10 (sequence SQ162).

  When the client 10 receives the getAllAsyncResults response from the proxy 20, it returns Ack to the proxy 20 (sequence SQ163).

By performing the processing as shown in FIG. 41, even for a large amount of document list acquisition processing, only the first 10 pages are acquired by a synchronous operation, and all subsequent pages are acquired by an asynchronous operation. The client 10 can execute other processes in parallel with the document list acquisition process.
(Large document list acquisition processing-some operations via proxy)
Hereinafter, an example of a large amount of document list acquisition processing when the asynchronous operation is used via the proxy 20 is shown in FIG. FIG. 42 is a sequence diagram showing a large amount of document list acquisition processing when the asynchronous operation is used via a proxy.

  First, the client 10 transmits an execute Search request for calling an execute Search operation, which is a synchronous operation, to the server 30 (sequence SQ170).

  When the server 30 receives an executeSearch request from the client 10, the server 30 starts searching the document list (executes the executeSearch operation). When the search of the document list is started, a response including a return value of the executeSearch operation is received. The data is transmitted to the requesting client 10 (sequence SQ171).

  When the client 10 receives a response including the return value of the executeSearch operation from the server 30, the client 10 transmits a getTop10Page request for calling the getTop10Page operation, which is a synchronous operation for acquiring the top 10 data of the search result, to the server 30. (Sequence SQ172).

  When the server 30 receives a getTop10Page request from the client 10, the server 30 acquires data (list data) corresponding to the top 10 search results (executes the getTop10Page operation), and the top 10 which are return values of the getTop10Page operation. The response including the minute data is transmitted to the requesting client 10 (sequence SQ173).

  Since the client 10 acquires only the top 10 data, it can be acquired quickly. For example, in response to a request from the user, only the acquired top 10 data can be quickly displayed on the display or the like. Can do.

  Further, when acquiring all the remaining list data, the client 10 transmits a getAllAsync request for invoking a getAllAsync operation that is an asynchronous operation to the proxy 20 (sequence SQ174).

  When the proxy 20 receives the getAllAsync request from the client 10, the proxy 20 returns Ack to the client 10 (sequence SQ175), while transmitting a getAll request for calling the getAll operation that is a synchronous operation to the server 30 (sequence SQ176).

  When the client 10 transmits the request, it immediately receives Ack from the proxy 20 so that other processing can be executed during the acquisition processing of all the remaining list data.

  Upon receiving a getAll request from the proxy 20, the server 30 executes an acquisition process (getAll operation) of all remaining list data. When the getAll operation is completed, server 30 transmits a getAllResults response including the acquisition of all the remaining list data, which is a return value of the getAll operation, to requesting proxy 20 (sequence SQ177).

  When the proxy 20 receives a getAllResults response from the server 30, the proxy 20 transmits a getAllAsyncResults response including data of all remaining pages to the requesting client 10 (sequence SQ178).

  When client 10 receives the getAllAsynchronouss response from proxy 20, client 10 returns Ack to proxy 20 (sequence SQ179).

By performing the processing as shown in FIG. 42, even for a large amount of document list acquisition processing, only the first 10 pages are acquired by a synchronous operation, and all subsequent pages are acquired by an asynchronous operation. The client 10 can execute other processes in parallel with the document list acquisition process.
(System configuration 1)
The system configuration of an example of an asynchronous operation providing system is shown in FIG. FIG. 43 is a system configuration diagram (part 1) of the asynchronous operation providing system.

  In the asynchronous operation providing system as shown in FIG. 43, the client 10, the proxy 20, and the server 30 are included in different devices. For example, in the asynchronous operation providing system of FIG. 43, the client 10 is included in the client device 1 and the like shown in FIG. 6, the proxy 20 is included in the proxy device 2 and the like shown in FIG. 8 is included in the server apparatus 3 shown in FIG.

  Hereinafter, FIG. 44 shows an example effective when the client 10, the proxy 20, and the server 30 are included in different devices. FIG. 44 is a diagram showing an example in which the asynchronous operation providing system shown in FIG. 43 is effective.

  As shown in FIG. 44, when a new system having the proxy 20 is introduced in an environment where an old system already exists, the system shown in FIG. 43 is effective.

(System configuration 2)
The system configuration of another example of the asynchronous operation providing system is shown in FIG. FIG. 45 is a system configuration diagram (part 2) of the asynchronous operation providing system.

  In the asynchronous operation providing system as shown in FIG. 45, the client 10 and the proxy 20 are included in the same device. For example, in the asynchronous operation providing system of FIG. 45, the client 10 and the proxy 20 are included in the client device 1 and the like shown in FIG. 6, for example, and the server 30 is included in the server device 3 and the like shown in FIG. .

  FIG. 46 shows an example effective when the client 10 and the proxy 20 are included in the same device. FIG. 46 is a diagram showing an example in which the asynchronous operation providing system shown in FIG. 45 is effective.

  As shown in FIG. 46, when an old client-server system already exists, the server 30 and the server apparatus 3 are not changed, and the new client apparatus 1 having the proxy 20 is introduced into the system. A system as shown in 43 is effective.

(System configuration 3)
The system configuration of another example of the asynchronous operation providing system is shown in FIG. FIG. 47 is a system configuration diagram (part 3) of the asynchronous operation providing system.

  In the asynchronous operation providing system as shown in FIG. 47, the proxy 20 and the server 30 are included in the same device. For example, in the asynchronous operation providing system of FIG. 47, the client 10 is included in the client device 1 and the like shown in FIG. 6, and the proxy 20 and the server 30 are included in the server device 3 and the like shown in FIG. .

  FIG. 48 shows an example effective when the proxy 20 and the server 30 are included in the same device. FIG. 48 is a diagram showing an example in which the asynchronous operation providing system shown in FIG. 47 is effective.

  As shown in FIG. 48, when the old client 10 and the client device 1 are not changed in the environment where the old client-server system already exists and the client 10 and the client device 1 are newly introduced into the system, A system as shown in FIG. 47 is effective.

  As described above, according to the present invention, it is possible to provide an asynchronous operation to a client even for a service that supports a synchronous operation and does not support an asynchronous operation.

  The preferred embodiments of the present invention have been described in detail above, but the present invention is not limited to such specific embodiments, and various modifications can be made within the scope of the gist of the present invention described in the claims.・ Change is possible.

It is a figure which shows an example of the service which supports only a synchronous operation. This is an example of a service that also supports asynchronous operations. It is a figure which shows the example of a general synchronous operation. It is a figure which shows the example of a general asynchronous operation (polling). It is a figure which shows the example of a general asynchronous operation (coldback). It is a hardware block diagram of an example of a client apparatus. It is a hardware block diagram of an example of a proxy apparatus. It is a hardware block diagram of an example of a server apparatus. It is a function block diagram (the 1) of a proxy. It is a sequence diagram which shows the case of polling as an asynchronous operation provision process via a proxy. It is a function block diagram (the 2) of a callback. FIG. 10 is a sequence diagram illustrating an asynchronous operation providing process via a proxy as an example of a callback. It is a function block diagram (the 1) of an asynchronous operation provision system. FIG. 6 is a diagram (part 1) illustrating an example in which a proxy address is described in a WSDL file. It is a conceptual diagram of an example in which an operation is used via a proxy after the server is informed of the proxy address. It is a function block diagram (the 2) of an asynchronous operation provision system. FIG. 10 is a second diagram illustrating an example in which a proxy address is described in a WSDL file. It is a sequence diagram (the 1) which shows the process which uses operation. It is a function block diagram (the 3) of an asynchronous operation provision system. FIG. 10 is a diagram (part 1) illustrating an example in which a proxy address is described in a WS-Policy file. It is a sequence diagram (the 2) which shows the process using an operation. FIG. 10 is a conceptual diagram of an example in which a client searches for a server and discovers the server, and then uses an operation via the proxy based on a correspondence table between the service (server) and the proxy that the client has. It is a function block diagram (the 4) of an asynchronous operation provision system. It is a figure which shows a service proxy correspondence table. FIG. 10 is a sequence diagram (part 1) illustrating target service designation processing. It is a figure which shows an example of operation which designates a target service. FIG. 10 is a sequence diagram (part 2) illustrating a target service designation process. It is a figure which shows the example which described the target service in the SOAP header. The synchronous operation is a conceptual diagram showing an example in which communication is directly performed with a server and the asynchronous operation is used via a proxy. It is a function block diagram (the 5) of an asynchronous operation provision system. FIG. 11 is a third diagram illustrating an example in which a proxy address is described in a WSDL file; It is a function block diagram (the 6) of an asynchronous operation provision system. FIG. 10 is a second diagram illustrating an example in which a proxy address is described in a WS-Policy file. FIG. 10 is a sequence diagram (No. 3) illustrating a process using an operation. FIG. 10 is a third diagram illustrating an example in which a proxy address is described in a WS-Policy file. It is a sequence diagram (the 4) which shows the process which utilizes operation. It is a function block diagram (the 7) of an asynchronous operation provision system. It is a figure which shows an operation proxy correspondence table. FIG. 10 is a sequence diagram showing a large amount of scan processing when all operations are routed through a proxy. Asynchronous operation is a sequence diagram showing a large amount of scan processing when used via a proxy. FIG. 10 is a sequence diagram showing a large amount of document list acquisition process when all operations are used via a proxy. Asynchronous operation is a sequence diagram showing a large amount of document list acquisition processing when used via a proxy. It is a system configuration | structure figure (the 1) of an asynchronous operation provision system. It is a figure which shows the example in which the asynchronous operation provision system shown in FIG. 43 is effective. It is a system configuration | structure figure (the 2) of an asynchronous operation provision system. It is a figure which shows the example in which the asynchronous operation provision system shown in FIG. 45 is effective. It is a system configuration | structure figure (the 3) of an asynchronous operation provision system. It is a figure which shows the example in which the asynchronous operation provision system shown in FIG. 47 is effective.

Explanation of symbols

1 Client device 2 Proxy device 3 Server device 10 Client (client service)
20 Proxy (proxy service)
30 servers (services)
41 Request Receiving Unit 42 Response Holding / Transmitting Unit 43 Asynchronous Thread 44 Synchronous Message Transmission / Reception Unit 51 Request Justin 52 Response Receiving Unit 53 Asynchronous Thread 54 Synchronous Message Transmission / Reception Unit

Claims (20)

A proxy device that supports a synchronous operation related to a service and that can provide an asynchronous operation related to the service to a service using unit that uses a service provided by a service providing unit that does not support an asynchronous operation related to the service. There,
Request receiving means for receiving a request from the service using means;
Asynchronous execution means that is generated in response to a use request for an asynchronous operation related to the service from the service use means, and executes processing related to the asynchronous operation;
In response to a request from the service using means, a response is sent to the service using means, while a processing result of the synchronous operation executed by the service providing means is temporarily held in response to the asynchronous operation use request. A response holding / transmitting means for sending to the service using means as a result of the asynchronous operation processing;
A proxy device comprising: A proxy device that supports a synchronous operation related to a service and that can provide an asynchronous operation related to the service to a service using unit that uses a service provided by a service providing unit that does not support an asynchronous operation related to the service. There,
Request receiving means for receiving a request from the service using means;
Asynchronous execution means that is generated in response to a use request for an asynchronous operation related to the service from the service use means, and executes processing related to the asynchronous operation;
In response to a request from the service using means, a response is sent to the service using means, while a processing result of the synchronous operation executed by the service providing means in response to the use request of the asynchronous operation is processed as an asynchronous operation. As a result, response transmitting means for transmitting to the service using means,
A proxy device comprising:   3. The proxy apparatus according to claim 1, wherein the asynchronous execution unit includes a synchronous message transmission / reception unit that transmits / receives a synchronous message to / from the service providing unit. A service using apparatus having service using means for using a service provided by service providing means that supports synchronous operation related to a service and does not support asynchronous operation related to a service,
The service using means acquires an address related to the proxy device according to any one of claims 1 to 3 described in an extension element in WSDL from the service providing means side, and the proxy device based on the address A service using device that communicates with the service. A service using apparatus having service using means for using a service provided by service providing means that supports synchronous operation related to a service and does not support asynchronous operation related to a service,
The service using unit acquires an address related to the proxy device according to any one of claims 1 to 3 described in WS-Policy from the service providing unit side, and based on the address, A service using device that performs communication. A service using apparatus having service using means for using a service provided by service providing means that supports synchronous operation related to a service and does not support asynchronous operation related to a service,
A proxy that manages, holds, and associates a service provided by the service providing unit or an operation related to the service provided by the service providing unit with an address related to the proxy device according to any one of claims 1 to 3. It further has a device management unit,
The service utilization unit acquires an address related to the proxy device from the proxy device management unit according to a service provided by the service providing unit or an operation related to a service provided by the service providing unit, Based on the above, the service use device communicates with the proxy device.   7. The service using unit according to claim 4, wherein the service using unit communicates with the service providing unit via the proxy device when using the synchronous operation and when using the asynchronous operation. The service utilization apparatus according to one item.   The service using means communicates directly with the service providing means when using the synchronous operation, and communicates with the service providing means via the proxy device when using the asynchronous operation. The service use apparatus according to claim 4, wherein the service use apparatus is characterized in that: Computer
A request receiving unit that receives a request from a service using unit that uses a service provided by a service providing unit that supports a synchronous operation related to a service and does not support an asynchronous operation related to the service;
Asynchronous execution means that is generated in response to a use request for an asynchronous operation related to the service from the service use means, and executes processing related to the asynchronous operation;
In response to a request from the service using means, a response is sent to the service using means, while a processing result of the synchronous operation executed by the service providing means is temporarily held in response to the asynchronous operation use request. A response holding / transmitting means for sending to the service using means as a result of the asynchronous operation processing;
A proxy program that enables the service utilization means to provide an asynchronous operation related to the service. Computer
A request receiving unit that receives a request from a service using unit that uses a service provided by a service providing unit that supports a synchronous operation related to a service and does not support an asynchronous operation related to the service;
Asynchronous execution means that is generated in response to a use request for an asynchronous operation related to the service from the service use means, and executes processing related to the asynchronous operation;
In response to a request from the service using means, a response is sent to the service using means, while a processing result of the synchronous operation executed by the service providing means in response to the use request of the asynchronous operation is processed as an asynchronous operation. As a result, response transmitting means for transmitting to the service using means,
A proxy program that enables the service utilization means to provide an asynchronous operation related to the service.   11. The proxy program according to claim 9, wherein the asynchronous execution unit includes a synchronous message transmission / reception unit that transmits / receives a synchronous message to / from the service providing unit. Computer
A service use program that supports a synchronous operation related to a service and operates as a service use means that uses a service provided by a service providing means that does not support an asynchronous operation related to a service,
The service using means acquires an address related to the proxy program according to any one of claims 9 to 11 described in an extension element in WSDL from the service providing means side, and based on the address, the proxy program A service use program characterized by communicating with. Computer
A service use program that supports a synchronous operation related to a service and operates as a service use means that uses a service provided by a service providing means that does not support an asynchronous operation related to a service,
The service using means acquires an address related to the proxy program according to any one of claims 9 to 11 described in WS-Policy from the service providing means side, and based on the address, A service use program characterized by performing communication. Computer
A service use program that supports a synchronous operation related to a service and operates as a service use means that uses a service provided by a service providing means that does not support an asynchronous operation related to a service,
The service using means associates the service provided by the service providing means or the operation related to the service provided by the service providing means with the address related to the proxy program according to any one of claims 9 to 11. The proxy program management unit obtains the address according to a service provided by the service providing unit or an operation related to a service provided by the service providing unit from the managing and holding proxy device management unit, and based on the address, the proxy program A service use program characterized by communicating with.   15. The service using unit according to claim 12, wherein the service using unit communicates with the service providing unit through the proxy program when using the synchronous operation and when using the asynchronous operation. The service utilization program described in one item.   The service using means communicates directly with the service providing means when using the synchronous operation, and communicates with the service providing means via the proxy program when using the asynchronous operation. The service use program according to any one of claims 12 to 14, characterized in that   The computer-readable recording medium which recorded the proxy program as described in any one of Claims 9 thru | or 11.   The computer-readable recording medium which recorded the service utilization program as described in any one of Claims 12 thru | or 16. An asynchronous operation providing method for providing an asynchronous operation related to a service to a service using means that uses a service provided by a service providing means that supports a synchronous operation related to a service and does not support an asynchronous operation related to a service. There,
A request receiving stage for receiving a request from the service using means;
Asynchronous execution means generating stage for generating asynchronous execution means for executing asynchronous processing in response to an asynchronous operation use request related to the service from the service using means;
In response to a request from the service using means, a response is sent to the service using means, while a processing result of the synchronous operation executed by the service providing means is temporarily held in response to the asynchronous operation use request. A response holding / sending stage to be sent to the service using means as a result of the asynchronous operation processing;
A method for providing an asynchronous operation, comprising: An asynchronous operation providing method for providing an asynchronous operation related to a service to a service using means that uses a service provided by a service providing means that supports a synchronous operation related to a service and does not support an asynchronous operation related to a service. There,
A request receiving stage for receiving a request from the service using means;
Asynchronous execution means generating stage for generating asynchronous execution means for executing asynchronous processing in response to an asynchronous operation use request related to the service from the service using means;
In response to a request from the service using means, a response is sent to the service using means, while a processing result of the synchronous operation executed by the service providing means in response to the use request of the asynchronous operation is processed as an asynchronous operation. As a result, a response transmission step for transmitting to the service using means,
A method for providing an asynchronous operation, comprising:

Images