Synchronous interface to asynchronous processes

• US 20050234928A1
• Filed: 03/23/2004
• Published: 10/20/2005
• Est. Priority Date: 03/23/2004
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: GrandCentral Communications Incorporated (Alphabet Inc.)
• Inventors: Lerner, Alexander, Boulos, Thomas Nabiel, Shkvarchuk, Taras
• Granted Patent: US 7,739,351 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 12/5601 Transfer mode dependent, e.g. ATM
• CPC Class Codes: H04L 2012/5619 Network Node Interface, e.g. tandem connections, transit switching
• CPC Class Codes: H04L 2012/5629 Admission control
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561

Abstract

Methods and apparatus, including computer program products, implementing and using techniques for selectively accessing one or more web services from a client machine, the one or more web services and the client machine being accessible over a network. A request for information is received from a client machine with a conversion engine. The request is received over a synchronous interface. The request is processed in the conversion engine. The processed request is transmitted over an asynchronous interface from the conversion engine to at least one web service. Methods and apparatus, including computer program products, for converting a web service description language file for a synchronous web service into a web service description language file for an asynchronous client machine are also described.

Claims

1. A computer-implemented method for selectively accessing one or more web services from a client machine, the one or more web services and the client machine being accessible over a network, the method comprising:

receiving a request for information from a client machine with a conversion engine, the request being received over a synchronous interface;

processing the request in the conversion engine; and

transmitting the processed request over an asynchronous interface from the conversion engine to at least one web service.

2. The computer-implemented method of claim 1, wherein the network is one of:

a local area network, and a wide area network.

3. The computer-implemented method of claim 1, further comprising:

receiving a response to the processed request from the at least one web service with the conversion engine, the response being received over the asynchronous interface;

processing the response in the conversion engine; and

transmitting the processed response over the synchronous interface from the conversion engine to the client machine.

4. The computer-implemented method of claim 1, wherein receiving a request further comprises:

blocking the client machine until one or more of the following events has occurred;

a response to the received request has been obtained from the web service and delivered to the client machine, an error message has been delivered to the client machine, and a predetermined time period has passed.

5. The computer-implemented method of claim 1, wherein processing the request comprises:

receiving the request at a synchronous post interface;

placing the request in a receive queue;

routing the request to one or more delivery queues; and

transferring the request from the delivery queues to one or more asynchronous push interfaces.

6. The computer-implemented method of claim 1, further comprising:

receiving a confirmation from the at least one web service over the asynchronous interface that the processed request has been received by the at least one web service.

7. The computer-implemented method of claim 1, wherein transmitting the processed request comprises:

pushing the processed request to the at least one web service over the asynchronous interface.

8. The computer-implemented method of claim 1, wherein transmitting the processed request comprises:

transmitting an available processed request to the at least one web service through the asynchronous interface in response to polling of the asynchronous interface by the at least one web service.

9. The computer-implemented method of claim 1, wherein processing the request comprises:

performing security management including one or more of;

authentication, authorization, security policy enforcement, decryption, and validation of digital signatures.

10. The computer-implemented method of claim 2, wherein processing the response comprises:

receiving the response at an asynchronous post interface;

placing the response in a receive queue; and

routing the response to a delivery queue for the client machine.

11. The computer-implemented method of claim 2, further comprising:

transmitting a confirmation to the at least one web service over the asynchronous interface that the response has been received by the conversion engine.

12. The computer-implemented method of claim 2, wherein transmitting the processed response comprises:

pushing the processed response to the client machine over the synchronous interface.

13. A conversion engine, comprising:

a synchronous interface operable to;

receive a request from a client machine communicating synchronously with the conversion engine over a network; and

deliver a response to the request from the conversion engine to the client machine over the wide area network;

an asynchronous interface operable to;

deliver the received request from the conversion engine to one or more web services communicating asynchronously over the wide area network; and

receive a response to the request from the one or more web services over the wide area network; and

a processing module operable to;

convert a synchronous request into an asynchronous request; and

convert an asynchronous response into a synchronous response.

14. The conversion engine of claim 13, wherein the network is one of:

a local area network, and a wide area network.

15. The conversion engine of claim 13, wherein the asynchronous interface further is operable to:

receive a confirmation from the at least one web service over the asynchronous interface that the processed request has been received by the at least one web service.

16. The conversion engine of claim 13, wherein the asynchronous interface further is operable to:

transmit a confirmation to the at least one web service over the asynchronous interface that the response has been received by the conversion engine.

17. The conversion engine of claim 13, further comprising:

a routing module operable to;

route a received request to one or more web services; and

route a received response to the request to the client machine.

18. The conversion engine of claim 13, further comprising:

a policy directory storing policies for performing security management including one or more of;

authentication, authorization, security policy enforcement, decryption, and validation of digital signatures.

19. The conversion engine of claim 13, further comprising:

a web service directory containing information about available web services and their communication interfaces.

20. The conversion engine of claim 19, wherein the web service directory includes one or more web service description language files for the available web services.

21. A computer-implemented method for converting a first web service description language file describing synchronous operations for a web service into a second web service description language file describing asynchronous operations, comprising:

providing a first web service description language file describing synchronous operations for a web service to a conversion engine;

translating the first web service description language file in the conversion engine into a second web service description language file describing asynchronous operations; and

providing the second web service description language file to the client machine for further generation of client machine code.

22. The computer-implemented method of claim 21, wherein translating includes one or more of the following operations:

translating a types part of the first web service description language file into a types part of the second web service description language file,

translating a message part of the first web service description language file into a message part of the second web service description language file,

translating a port type part of the first web service description language file into a port type part of the second web service description language file,

translating a bindings part of the first web service description language file into a bindings part of the second web service description language file, and

translating a service part of the first web service description language file into a service part of the second web service description language file.

23. The computer-implemented method of claim 22, wherein translating a types part comprises:

preserving any data structures defined in the first web service description language file in the second web service description language file.

24. The computer-implemented method of claim 22, wherein translating a types part comprises:

adding an acknowledge element in the asynchronous web service description language file, the acknowledge element describing an acknowledgement that is returned when a request is asynchronously posted to the conversion engine by the client machine.

25. The computer-implemented method of claim 24, wherein the acknowledgement includes a correlation identifier.

26. The computer-implemented method of claim 25, wherein the correlation identifier is one or more of:

a session identifier, a token, and a call identifier.

27. The computer-implemented method of claim 22, wherein translating a message part comprises:

adding messages to the asynchronous web service description language file that are particular to asynchronous communication, the messages including one or more of;

a message for returning an acknowledgement response, a message for polling, a message for acknowledging a received request, and a message for acknowledging a response from a web service.

28. The computer-implemented method of claim 27, wherein the message for polling includes one or more of:

a message for polling using a session identifier, a message for polling using a topic, and a message for polling using a token.

29. The computer-implemented method of claim 22, wherein translating a port type part comprises:

inserting a port type for asynchronous post operations and a port type for asynchronous poll operations into the second web service description language file.

30. The computer-implemented method of claim 29, wherein the port type contains one or more of the following polling options:

polling by session identifier, polling by topic, and polling by token.

31. The computer-implemented method of claim 22, wherein translating a bindings part comprises:

inserting binding for a post port type;

inserting a binding for a poll port type; and

setting an encoding for messages that include the port types to reflect the encoding used by the conversion engine.

32. The computer-implemented method of claim 22, wherein translating a service part comprises:

adding an asynchronous post port with a first uniform resource locator addressing the conversion engine, and an asynchronous poll port with a second uniform resource locator to the conversion engine.

33. The computer-implemented method of claim 22, wherein translating comprises:

using a template stored in the conversion engine for translating at least part of the synchronous web service description language file into the asynchronous web service description language file.

34. A computer-implemented method for converting a first web service description language file describing asynchronous operations for a web service into a second web service description language file describing synchronous operations, comprising:

providing a first web service description language file describing asynchronous operations for a web service to a conversion engine;

translating the first web service description language file in the conversion engine into a second web service description language file describing synchronous operations; and

providing the second web service description language file to the client machine for further generation of client machine code.

35. The computer-implemented method of claim 34, wherein translating includes one or more of the following operations:

translating a types part of the first web service description language file into a types part of the second web service description language file,

translating a message part of the first web service description language file into a message part of the second web service description language file,

translating a port part of the first web service description language file into a port part of the second web service description language file,

translating a bindings part of the first web service description language file into a bindings part of the second web service description language file, and

translating a service part of the first web service description language file into a service part of the second web service description language file.

36. A computer program product, stored on a machine-readable medium, comprising instructions operable to cause a computer to:

receive a request for information from a client machine with a conversion engine, the request being received over a synchronous interface;

process the request in the conversion engine; and

transmit the processed request over an asynchronous interface from the conversion engine to at least one web service.

37. The computer program product of claim 36, further comprising instructions to:

receive a response to the processed request from the at least one web service with the conversion engine, the response being received over the asynchronous interface;

process the response in the conversion engine; and

transmit the processed response over the synchronous interface from the conversion engine to the client machine.

38. The computer program product of claim 36, wherein the instructions to receive a request further comprise instructions to:

block the client machine until one or more of the following events has occurred;

a response to the received request has been obtained from the web service and delivered to the client machine, an error message has been delivered to the client machine, and a predetermined time period has passed.

39. The computer program product of claim 36, wherein the instructions to process the request comprise instructions to:

receive the request at a synchronous post interface;

place the request in a receive queue;

route the request to one or more delivery queues; and

transfer the request from the delivery queues to one or more asynchronous push interfaces.

40. The computer program product of claim 36, wherein the instructions to process the request comprise instructions to:

perform security management including one or more of;

authentication, authorization, security policy enforcement, decryption, and validation of digital signatures.

41. The computer program product of claim 36, wherein the instruction to process the response comprise instructions to:

receive the response at an asynchronous post interface;

place the response in a receive queue; and

route the response to a delivery queue for the client machine.

42. A computer program product, stored on a machine-readable medium, for converting a first web service description language file describing synchronous operations for a web service into a second web service description language file describing asynchronous operations, comprising instructions operable to cause a computer to:

provide a first web service description language file describing synchronous operations for a web service to a conversion engine;

translate the first web service description language file in the conversion engine into an second web service description language file describing asynchronous operations; and

provide the second web service description language file to the client machine for further generation of client machine code.

43. The computer program product of claim 42, wherein the instructions to translate include instructions to perform one or more of:

translate a types part of the first web service description language file into a types part of the second web service description language file,

translate a message part of the first web service description language file into a message part of the second web service description language file,

translate a port part of the first web service description language file into a port part of the second web service description language file,

translate a bindings part of the first web service description language file into a bindings part of the second web service description language file, and

translate a service part of the first web service description language file into a service part of the second web service description language file.

44. The computer program product of claim 43, wherein the instructions to translate a types part comprise instructions to:

preserve any data structures defined in the first web service description language file in the second web service description language file.

45. The computer program product of claim 43, wherein the instructions to translate a type part comprise instructions to:

add an acknowledge element in the asynchronous web service description language file, the acknowledge element describing an acknowledgement that is returned when a request is asynchronously posted to the conversion engine by the client machine.

46. The computer program product of claim 45, wherein the acknowledgement includes a correlation identifier.

47. The computer program product of claim 46, wherein the correlation identifier is one or more of:

a session identifier, a token, and a call identifier.

48. The computer program product of claim 43, wherein the instructions to translate a message part comprise instructions to:

add messages to the asynchronous web service description language file that are particular to asynchronous communication, the messages including one or more of;

a message for returning an acknowledgement, a message for polling, a message for acknowledging a received request, and a message for acknowledging a response from a web service.

49. The computer program product of claim 48, wherein the message for polling includes one or more of:

a message for polling using a session identifier, a message for polling using a topic, a message for polling using a token.

50. The computer program product of claim 43, wherein the instructions to translate a port part comprise instructions to:

insert a post port for asynchronous operation and a poll port for asynchronous operation into the second web service description language file.

51. The computer program product of claim 50, wherein the port type contains one or more of the following polling options:

polling by session identifier, polling by topic, and polling by token.

52. The computer program product of claim 43, wherein the instructions to translate a bindings part comprise instructions to:

insert a binding for a post port type;

insert a binding for a poll port type; and

set an encoding for the messages that include the port types to reflect the encoding used by the conversion engine.

53. The computer program product of claim 43, wherein the instructions to translate a service part comprise instructions to:

add an asynchronous post port with a first uniform resource locator addressing the conversion engine, and an asynchronous poll port with a second uniform resource locator to the conversion engine.

54. The computer program product of claim 43, wherein the instructions to translate comprise instructions to:

use a template stored in the conversion engine for translating at least part of the synchronous web service description language file into the asynchronous web service description language file.