Apparatus, system, and method for converting a synchronous interface into an asynchronous interface

• US 8,055,821 B2
• Filed: 11/17/2004
• Issued: 11/08/2011
• Est. Priority Date: 11/17/2004
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Peipelman, Jason Lee, Gimness, Joseph Andrew, McCain, Brian Sean
• Primary Examiner(s): Hafiz; Tariq
• Assistant Examiner(s): YU, HENRY W
• Application Number:
  US10/991,271
• Publication Number:
  US 20060117322A1
• Time in Patent Office: 2,547 Days
• Field of Search: None
• US Class Current: 710/58
• CPC Class Codes: G06F 9/54 Interprogram communication

Abstract

An apparatus, system, and method are disclosed for converting a synchronous interface into an asynchronous interface. The apparatus includes a receive module, a generate module, and a return module. The receive module receives a request for a transaction from a synchronous requester, the generate module generates a delaying object and a forwarding interface compatible with the requested return type, and the return module returns the delaying object with the forwarding interface to the requester. Additionally, services for implementing such an apparatus, system, and method are disclosed. Implementation of the apparatus, system, and method provide for increased computing performance, reduced application run time, and decreased usage of computing resources.

Claims

1. An apparatus to convert a synchronous interface into an asynchronous interface, the apparatus comprising:

a receive module comprising executable code stored on a storage device, executed by a processor, and configured to receive a request for a transaction from a synchronous requestor;

a generate module comprising executable code stored on the storage device, executed by the processor, and configured to generate a delaying object and a forwarding interface compatible with a requested return type, wherein the delaying object is configured as an IOU object defined by a JAVA®

IOU data class and performs a standby( ) operation indicating that the transaction is in process; and

a return module comprising executable code stored on the storage device, executed by the processor, and configured to return the delaying object with the forwarding interface to the requestor;

a satisfy module comprising executable code stored on the storage device, executed by the processor, and configured to satisfy the request for the transaction from the synchronous requestor by recognizing the delaying object as a completed transaction until the transaction is available for completion wherein the requestor continues to process other transactions until the transaction is available for completion;

a notification module comprising executable code stored on the storage device, executed by the processor, and configured to notify the synchronous requestor via the delaying object when the transaction is available for completion; and

an initiation module comprising executable code stored on the storage device, executed by the processor, and configured to initiate a second request for the transaction via the delaying object when the transaction is available for completion.

2. The apparatus of claim 1, further comprising a block module comprising executable code stored on the storage device, executed by the processor, and configured to block further requests for the transaction from the synchronous requestor until the transaction is available for completion.

3. The apparatus of claim 1, wherein the requestor simultaneously sends requests for transactions and processes returns for previously requested transactions.

4. The apparatus of claim 1, further comprising a completion module comprising executable code stored on the storage device, executed by the processor, and configured to complete the transaction by returning an object of the requested return type.

5. An apparatus to convert a synchronous interface into an asynchronous interface, the apparatus comprising:

a requesting module comprising executable code stored on a storage device, executed by a processor, and configured to send a request for a transaction;

a receiving module comprising executable code stored on the storage device, executed by the processor, and configured to receive a delaying object via an associated forwarding interface, wherein the delaying object is configured as an IOU object defined by a JAVA®

IOU data class and performs a standby( ) operation indicating that the transaction is in process;

a processing module comprising executable code stored on the storage device, executed by the processor, and configured to continue processing tasks in response to receiving the delaying object, receive a satisfaction for the request by recognizing the delaying object as a completed transaction until the transaction is available for completion, receive a notification via the delaying object when the transaction is available for completion, and in response to an initiation, make a second request for the transaction via the delaying object when the transaction is available for completion.

6. A system to convert a synchronous interface into an asynchronous interface, the system comprising:

a synchronous requestor configured to send a request for a transaction; and

a responder configured to receive the request for the transaction from a synchronous requestor, generate a delaying object and a forwarding interface compatible with a requested return type, wherein the delaying object is configured as an IOU object defined by a JAVA®

IOU data class and performs a standby( ) operation indicating that the transaction is in process, return the delaying object with the forwarding interface to the requestor, and satisfy the request for the transaction from the synchronous requestor by the synchronous requestor recognizing the delaying object as a completed transaction until the transaction is available for completion wherein the requestor continues to process other transactions until the transaction is available for completion;

the synchronous requester further configured to receive the delaying object with the associated forwarding interface, and continue to process tasks in response to receiving the delaying object and the satisfaction of the transaction request; and

the responder further configured to notify the synchronous requestor via the delaying object when the transaction is available for completion and initiate a second request for the transaction via the delaying object when the transaction is available for completion.

7. The system of claim 6, wherein the responder is further configured to block further requests for the transaction from the synchronous requestor until the transaction is available for completion.

8. The system of claim 6, wherein the responder is further configured to complete the transaction by returning an object of the requested return type.

9. The system of claim 8, wherein the requestor simultaneously sends requests for transactions and processes returns for previously requested transactions.

10. A program of executable code stored on a storage device, executed by a processor, and configured to perform operations for converting a synchronous interface to an asynchronous interface, the operations comprising:

receiving a request for a transaction from a synchronous requestor;

generating a delaying object and a forwarding interface compatible with a requested return type, wherein the delaying object is configured as an IOU object defined by a JAVA®

IOU data class and performs a standby( ) operation indicating that the transaction is in process;

returning the delaying object with the forwarding interface to the requestor;

satisfying the request for the transaction from the synchronous requestor by recognizing the delaying object as a completed transaction until the transaction is available for completion wherein the requestor continues to process other transactions until the transaction is available for completion;

notifying the synchronous requestor via the delaying object when the transaction is available for completion; and

initiating a second request for the transaction via the delaying object when the transaction is available for completion.

11. The program of claim 10, wherein the instructions further comprise an operation to block further requests for the transaction from the synchronous requestor until the transaction is available for completion.

12. The program of claim 10, wherein the requestor simultaneously sends requests for transactions and processes returns for previously requested transactions.

13. The program of claim 10, wherein further comprising an operation to complete the transaction by returning an object of the requested return type.

14. A method for providing a service of converting a synchronous interface into an asynchronous interface, the method comprising:

receiving a request for a transaction from a synchronous requestor;

generating a delaying object and a forwarding interface compatible with a requested return type, wherein the delaying object is configured as an IOU object defined by a JAVA®

IOU data class and performs a standby( ) operation indicating that the transaction is in process; and

returning the delaying object with the forwarding interface to the requestor;

satisfying the request for the transaction from the synchronous requestor by recognizing the delaying object as a completed transaction until the transaction is available for completion wherein the requestor continues to process other transactions until the transaction is available for completion;

notifying the synchronous requestor via the delaying object when the transaction is available for completion; and

initiating a second request for the transaction via the delaying object when the transaction is available for completion.

15. The method of claim 14, wherein completing the transaction further comprises returning an object of the requested return type via the delaying object.

16. An apparatus to convert a synchronous interface into an asynchronous interface, the apparatus comprising:

means for receiving a request for a transaction from a synchronous requestor, the receiving means comprising executable code stored on a storage device and executed by a processor;

means for generating a delaying object and a forwarding interface compatible with a requested return type, wherein the delaying object is configured as an IOU object defined by a JAVA®

IOU data class and performs a standby( ) operation indicating that the transaction is in process, the generating means comprising executable code stored on the storage device and executed by the processor;

means for returning the delaying object with the forwarding interface to the requestor, the returning means comprising executable code stored on the storage device and executed by the processor;

means for satisfying the request for the transaction from the synchronous requestor by recognizing the delaying object as a completed transaction until the transaction is available for completion wherein the requestor continues to process other transactions until the transaction is available for completion, the satisfying means comprising executable code stored on the storage device and executed by the processor;

means for notifying the synchronous requestor via the delaying object when the transaction is available for completion, the notifying means comprising executable code stored on the storage device and executed by the processor; and

means for initiating a second request for the transaction via the delaying object when the transaction is available for completion, the initiating means comprising executable code stored on the storage device and executed by the processor.