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

• US 20060117322A1
• Filed: 11/17/2004
• Published: 06/01/2006
• Est. Priority Date: 11/17/2004
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Peipelman, Jason Lee, Gimness, Joseph Andrew, McCain, Brian Sean
• Granted Patent: US 8,055,821 B2
• Time in Patent Office: Days
• US Class Current: 719/314
• 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 configured to receive a request for a transaction from a synchronous requester;

a generate module configured to generate a delaying object and a forwarding interface compatible with the requested return type; and

a return module configured to return the delaying object with the forwarding interface to the requestor.

2. The apparatus of claim 1, further comprising a block module 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, further comprising a satisfy module configured to satisfy the request for the transaction from the synchronous requester until the transaction is available for completion.

4. The apparatus of claim 1, wherein the requestor continues to process other transactions until the transaction is available for completion.

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

6. The apparatus of claim 1, further comprising a notification module configured to notify the synchronous requestor via the delaying object when the transaction is available for completion.

7. The apparatus of claim 1, further comprising an initiation module configured to initiate a second request for the transaction via the delaying object when the transaction is available for completion.

8. The apparatus of claim 1, further comprising a completion module configured to complete the transaction by returning an object of the expected type.

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

a requesting module configured to send a request for a transaction;

a receiving module configured to receive a delaying object via an associated forwarding interface; and

a processing module configured to continue processing tasks in response to receiving the delaying object.

10. 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, receive a delaying object with an associated forwarding interface, and continue to process tasks in response to receiving the delaying object; and

a responder configured to receive a request for a transaction from a synchronous requester, generate a delaying object and a forwarding interface compatible with the requested return type, and return the delaying object with the forwarding interface to the requestor.

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

12. The system of claim 11, wherein the responder is further configured to satisfy the request for the transaction from the synchronous requestor until the transaction is available for completion.

13. The system of claim 12, wherein the responder is further configured to notify the synchronous requester via the delaying object when the transaction is available for completion.

14. The system of claim 13, wherein the responder is further configured to initiate a second request for the transaction via the delaying object when the transaction is available for completion.

15. The system of claim 14, wherein the responder is further configured to complete the transaction by returning an object of the expected type.

16. The system of claim 15, wherein the requestor continues to process other transactions until the transaction is available for completion.

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

18. A signal bearing medium tangibly embodying a program of machine-readable instructions executable by a digital processing apparatus to perform operations for converting a synchronous interface to an asynchronous interface, the operations comprising:

receiving a request for a transaction from a synchronous requester;

generating a delaying object and a forwarding interface compatible with the requested return type; and

returning the delaying object with the forwarding interface to the requester.

19. The signal bearing medium of claim 18, 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.

20. The signal bearing medium of claim 18, wherein the instructions further comprise an operation to satisfy the request for the transaction from the synchronous requestor until the transaction is available for completion.

21. The signal bearing medium of claim 18, wherein the requestor continues to process other transactions until the transaction is available for completion.

22. The signal bearing medium of claim 18, wherein the requestor simultaneously sends requests for transactions and processes returns for previously requested transactions.

23. The signal bearing medium of claim 18, wherein the instructions further comprise an operation to notify the synchronous requestor via the delaying object when the transaction is available for completion.

24. The signal bearing medium of claim 18, wherein the instructions further comprise an operation to initiate a second request for the transaction via the delaying object when the transaction is available for completion.

25. The signal bearing medium of claim 18, wherein the instructions further comprise an operation to complete the transaction by returning an object of the expected type.

26. 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 requester;

generating a delaying object and a forwarding interface compatible with the requested return type; and

returning the delaying object with the forwarding interface to the requester.

27. The method of claim 26, wherein the method further comprises enabling the requester to continue processing other transactions until receiving notification that the transaction is available for completion.

28. The method of claim 26, wherein the method further comprises:

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

initiating a second request for the transaction via the delaying object; and

completing the transaction by returning an object of the expected type.

29. The method of claim 26, wherein completing the transaction further comprises returning an object of the expected type via the delaying object.

30. 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;

means for generating a delaying object and a forwarding interface compatible with the requested return type; and

means for returning the delaying object with the forwarding interface to the requester.