Method and apparatus for providing a synchronous interface for an asynchronous service

• US 7,970,814 B2
• Filed: 05/19/2009
• Issued: 06/28/2011
• Est. Priority Date: 05/20/2008
• Status: Active Grant

• Current Assignee: Raytheon Company (Rtx Corporation)
• Original Assignee: Raytheon Company (Rtx Corporation)
• Inventors: Spencer, George W. Jr., Carey, Kenneth D., Leedberg, Gregory
• Primary Examiner(s): Dharia; Rupal D
• Assistant Examiner(s): Fan; Hua
• Application Number:
  US12/468,100
• Publication Number:
  US 20090292765A1
• Time in Patent Office: 770 Days
• Field of Search: 709/202
• US Class Current: 709/202
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications

Abstract

Methods and apparatus for providing a synchronous interface for an asynchronous service including, in a synchronous interface engine executing on a processor, receiving a request from a client for the asynchronous service, issuing an asynchronous service request to perform the asynchronous service, the asynchronous service request including a unique client identifier, and associating a wait condition with the unique client identifier to indicate to the client to wait for a result of the asynchronous service. Methods and apparatus further include receiving the result of the asynchronous service, the result including the unique client identifier, removing the associated wait condition, and sending the result to the client.

Claims

1. A method, comprising:

in a synchronous interface engine executing on a processor to provide the synchronous interface, receiving a first request from a first client for a first asynchronous service;

issuing a first asynchronous service request to perform the first asynchronous service, the first asynchronous service request including a first unique client identifier associated with the first client;

associating a first wait condition with a first semaphore and the first unique client identifier to indicate to the first client to wait for a first result of the first asynchronous service, the associating comprising representing the first request in a first row of a hash table comprising;

the first unique client identifier; and

the first semaphore representing the associated first wait condition;

acquiring the first semaphore;

representing a second request associated with a second client in a second row of the hash table comprising a second unique client identifier associated with the second client and a second semaphore representing an associated second wait condition;

receiving the first result of the first asynchronous service, the first result including the first unique client identifier;

removing the associated first wait condition comprising;

locating the first unique client identifier in the first row of the hash table; and

releasing the first semaphore represented in the first row of the hash table; and

sending the first result to the first client.

2. The method of claim 1, wherein the first client waits until the first semaphore is released.

3. The method of claim 1 further comprising:

in an asynchronous request broker, receiving a request from a client for the asynchronous service, associating a unique client identifier with the client, and issuing an asynchronous service request to perform the asynchronous service, the asynchronous service request including the unique client identifier;

in a wait condition processor, associating a wait condition with the unique client identifier to indicate to the client to wait for a result of the asynchronous service, and;

in an asynchronous result broker, receiving the result of the asynchronous service, the result including the unique client identifier, and removing the associated wait condition,

wherein upon removing of the associated wait condition, the wait condition processor sends the result to the client.

8. The method of claim 1, further comprising:

in the synchronous interface engine, receiving the second request from the second client for a second asynchronous service;

issuing a second asynchronous service request to perform the second asynchronous service, the second asynchronous service request including the second unique client identifier associated with the second client; and

associating the second wait condition with the second semaphore and the second unique client identifier to indicate to the second client to wait for a second result of the second asynchronous service.

9. The method of claim 8, further comprising:

acquiring the second semaphore;

receiving the second result of the second asynchronous service, the second result including the second unique client identifier;

removing the associated second wait condition comprising;

locating the second unique client identifier in the second row of the hash table; and

releasing the second semaphore represented in the second row of the hash table; and

sending the second result to the second client.

4. An apparatus, comprising:

a microprocessor;

a synchronous interface engine executing on the microprocessor to provide the synchronous interface, comprising;

an asynchronous request broker configured to;

receive a first request from a first client for a first asynchronous service;

associate a first unique client identifier with the first client; and

issue a first asynchronous service request to perform the first asynchronous service, the first asynchronous service request including the first unique client identifier;

a wait condition processor configured to;

associate a first wait condition with a first semaphore and the first unique client identifier to indicate to the first client to wait for a first result of the asynchronous service, associate the first wait condition comprises representing the first request in a first row of a hash table comprising the first unique client identifier and the first semaphore representing the associated first wait condition;

acquire the first semaphore;

represent a second request associated with a second client in a second row of the hash table comprising a second unique client identifier associated with the second client and a second semaphore representing an associated second wait condition; and

an asynchronous result broker configured to;

receive the first result of the first asynchronous service, the first result including the first unique client identifier; and

remove the first associated wait condition comprising;

locating the first unique client identifier in the first row of the hash table; and

releasing the first semaphore represented in the first row of the hash table row,

wherein upon removing of the first associated wait condition, the wait condition processor sends the first result to the first client.

5. The apparatus of claim 4, wherein the wait condition processor waits until the first semaphore is released.

10. The apparatus of claim 4 wherein the asynchronous request broker is further configured to:

receive the second request from the second client for a second asynchronous service;

associate a second unique client identifier with the second client; and

issue a second asynchronous service request to perform the second asynchronous service, the second asynchronous service request including the second unique client identifier.

11. The apparatus of claim 10 wherein the wait condition processor is further configured to:

associate a second wait condition with a second semaphore and the second unique client identifier to indicate to the second client to wait for a second result of the asynchronous service; and

acquire the second semaphore.

12. The apparatus of claim 11 wherein the asynchronous result broker is further configured to:

receive the second result of the second asynchronous service, the second result including the second unique client identifier; and

remove the second associated wait condition comprising;

locating the second unique client identifier in the second row of the hash table; and

releasing the second semaphore represented in the second row of the hash table,

wherein upon removing of the second associated wait condition, the wait condition processor sends the second result to the second client.

6. An article, comprising:

a non-transitory storage medium having stored instructions thereon that when executed by a machine result in a synchronous interface for an asynchronous service enabling;

in a synchronous interface engine executing on a processor to provide the synchronous interface, receiving a first request from a first client for a first asynchronous service;

issuing a first asynchronous service request to perform the first asynchronous service, the first asynchronous service request including a first unique client identifier associated with the first client;

associating a first wait condition with a first semaphore and the first unique client identifier to indicate to the first client to wait for a first result of the first asynchronous service, the associating comprising representing the first request in a first row of a hash table comprising;

the first unique client identifier; and

the first semaphore representing the associated first wait condition;

acquiring the first semaphore;

representing a second request associated with a second client in a second row of the hash table comprising a second unique client identifier associated with the second client and a second semaphore representing an associated second wait condition;

receiving the first result of the first asynchronous service, the first result including the first unique client identifier;

removing the associated first wait condition comprising;

locating the first unique client identifier in the first row of the hash table; and

releasing the first semaphore represented in the first row of the hash table; and

sending the first result to the first client.

7. The article of claim 6, wherein the client waits until the first semaphore is released.

13. The article of claim 6 wherein the storage medium further comprises instructions enabling:

in the synchronous interface engine, receiving the second request from the second client for a second asynchronous service;

issuing a second asynchronous service request to perform the second asynchronous service, the second asynchronous service request including the second unique client identifier associated with the second client; and

associating the second wait condition with the second semaphore and the second unique client identifier to indicate to the second client to wait for a second result of the second asynchronous service.

14. The article of claim 13 wherein the storage medium further comprises instructions enabling:

acquiring the second semaphore;

receiving the second result of the second asynchronous service, the second result including the second unique client identifier;

removing the associated second wait condition comprising;

locating the second unique client identifier in the second row of the hash table; and

releasing the second semaphore represented in the second row of the hash table; and

sending the second result to the second client.