SYSTEMS AND METHODS FOR ASYNCHRONOUS NOTIFICATION USING HTTP

• US 20120131083A1
• Filed: 11/24/2010
• Published: 05/24/2012
• Est. Priority Date: 11/24/2010
• Status: Abandoned Application

• Current Assignee: ICEsoft Technologies Canada Corp.
• Original Assignee: ICEsoft Technologies Canada Corp.
• Inventors: GODDARD, EDWARD WAYNE, Ooststroom, Jeroen van
• Application Number:
  US12/954,510
• Publication Number:
  US 20120131083A1
• Time in Patent Office: Days
• US Class Current: 709/201
• CPC Class Codes: H04L 12/1859 adapted to provide push services, e.g. data channels
• CPC Class Codes: H04L 51/224 providing notification on incoming messages, e.g. pushed notifications of received messages
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

Methods and apparatus for asynchronous notification using HTTP. An application server configured to host one or more web applications and process HTTP requests associated with the one or more web applications includes a long polling mechanism configured to maintain an open HTTP connection, and a notification server configured to provide an asynchronous notification to one or more notification clients through the open HTTP connection, wherein the notification includes an identifier for the one or more notification clients with no application data payload.

Claims

1. An application server configured to host one or more web applications and process HTTP requests associated with the one or more web applications, comprising:

a long polling mechanism configured to maintain an open HTTP connection; and

a notification server configured to provide an asynchronous notification to one or more notification clients through the open HTTP connection, wherein the notification includes an identifier for the one or more notification clients with no application data payload.

2. The application server of claim 1 further comprising a notification-enabled application that includes the notification server.

3. The application server of claim 2 wherein the notification server is further configured to provide the notification in response to a notification trigger for the notification-enabled application, wherein the notification trigger contains a group name, and wherein the one or more notification clients are members of the group.

4. The application server of claim 3 wherein the notification-enabled application is configured to determine the group name and the group members.

5. The application server of claim 4 wherein the notification-enabled application is further configured to register with the notification server the group name and the identifier for the members of the group.

6. The application server of claim 5 wherein the notification server is further configured to use the registration to provide the notification with the identifier to the one or more notification clients in response to the notification trigger containing the group name.

7. The application server of claim 5 wherein the notification-enabled application is further configured to de-register one or more of the group members from the group.

8. The application server of claim 1 further comprising one or more notification-enabled applications, wherein the notification server is further configured provide the notification in response to a notification trigger for any one of the one or more notification-enabled applications.

9. The application server of claim 8 wherein the notification server is further configured to receive a notification tag from said any one of the one or more notification-enabled applications.

10. The application server of claim 9 wherein the notification server is further configured to provide the notification tag with the notification to the one or more notification clients through the open HTTP connection.

11. The application server of claim 10 wherein the notification server is further configured to receive a copy of the notification tag from one of the one or more notification clients with the next HTTP request from said one of the one or more notification clients.

12. The application server of claim 11 wherein the notification server is further configured to receive a subsequent notification trigger for a subsequent notification and subsequent notification tag from said any one of the one or more notification-enabled applications, and wherein the notification server is further configured to compare the copy of the notification tag received from said one of the one or more notifications clients with the subsequent notification tag.

13. The application server of claim 12 wherein the notification server is further configured to discard the subsequent notification if the copy of the notification tag received from said one of the one or more notification clients matches the subsequent notification tag.

14. The application server of claim 8 wherein the one or more notification-enabled applications comprise a plurality of notification-enabled applications.

15. The application server of claim 8 wherein said any one of the one or more notification-enabled applications comprises a notification server proxy configured to deliver the notification trigger for said any one of the one or more notification-enabled applications to the notification server.

16. The application server of claim 8 wherein the notification trigger contains a group name, wherein the one or more notification clients are members of the group.

17. The application server of claim 16 wherein said any one of the one or more notification-enabled applications is configured to determine the group name and the group members.

18. The application server of claim 17 wherein said any one of the one or more notification-enabled applications is further configured to register with the notification server the group name and the identifier for the members of the group.

19. The application server of claim 18 wherein said any one of the one or more notification-enabled applications comprises a notification server proxy, wherein said any one of the one or more notification-enabled applications is further configured to register with the notification server proxy the group name and the identifier for the members of the group, and wherein the notification server proxy is configured to forward the registration to the notification server.

20. The application server of claim 18 wherein the notification server is further configured to use the registration to provide the notification with the identifier to the one or more notification clients in response to the notification trigger containing the group name.

21. The application server of claim 18 wherein said any one of the one or more notification-enabled applications is further configured to de-register one or more of the group members from the group.

22. The application server of claim 1 wherein the notification server is further configured to provide the notification to one or more other applications servers in a cluster environment.

23. The application server of claim 1 wherein the notification server is further configured to receive the notification provided to the one or more notification clients from another application server in a cluster environment.

24. A method of providing asynchronous communications from an application server configured to host one or more web applications and process HTTP requests associated with the one or more web applications, the method comprising:

maintaining an open HTTP connection; and

providing an asynchronous notification to one or more notification clients through the open HTTP connection, wherein the notification includes an identifier for the one or more notification clients with no application data payload.

25. The method of claim 24 wherein the notification is provided to the one or more notification clients in response to a notification trigger, wherein the notification trigger contains a group name, and wherein the one or more notification clients are members of the group.

26. The method of claim 25 further comprising determining the group name and the group members.

27. The method of claim 26 further comprising registering the group name and the identifier for the members of the group.

28. The method of claim 27 further comprising using the registration to provide the notification with the identifier to the one or more notification clients in response to the notification trigger containing the group name.

29. The method of claim 27 further comprising de-registering one or more of the group members from the group.

30. The method of claim 24 further comprising providing a notification tag for any one of one or more notification-enabled applications with the notification to the one or more notification clients through the open HTTP connection.

31. The method of claim 30 further comprising receiving a copy of the notification tag from one of the one or more notification clients with the next HTTP request from said one of the one or more notification clients.

32. The method of claim 31 further comprising comparing the copy of the notification tag received from said one of the one or more notification clients with a subsequent notification tag associated with a subsequent notification.

33. The method of claim 32 further comprising discarding the subsequent notification in response to the copy of the notification tag received from said one of the one or more notification clients matching the subsequent notification tag.

34. The method of claim 24 further comprising providing the notification to one or more other applications servers in a cluster environment.

35. The method of claim 24 further comprising receiving the notification provides to the one or more notification clients from another application server in a cluster environment.

36. A machine-readable medium comprising instructions executable by a one or more processors to provide asynchronous communications from an application server configured to host one or more web applications and process HTTP requests associated with the one or more web applications, the instructions comprising:

code for maintaining an open HTTP connection; and

code for providing an asynchronous notification to one or more notification clients through the open HTTP connection, wherein the notification includes an identifier for the one or more notification clients with no application data payload.

37. The machine-readable medium of claim 36 wherein the code for providing the notification is configured to provide the notification in response to a notification trigger for a notification-enabled application, wherein the notification trigger contains a group name, and wherein the one or more notification clients are members of the group.

38. The machine-readable medium of claim 37 wherein the instructions further comprise code for the notification-enabled application to register the group name and an identifier for the members of the group.

39. The machine-readable medium of claim 38 wherein the code for providing the notification is configured to use the registration to provide the notification with the identifier to the one or more notification clients in response to the notification trigger containing the group name.

40. The machine-readable medium of claim 37 wherein the instructions further comprises code for the notification-enabled application to de-register one or more of the group members from the group.

41. The machine-readable medium of claim 36 wherein the code for providing the notification is configured to provide a notification tag for any one of one or more notification-enabled applications with the notification to the one or more notification clients through the open HTTP connection.

42. The machine-readable medium of claim 41 wherein the code for providing the notification is configured to provide the notification to the one or more notification clients with a notification tag for said any one of the one or more notification-enabled applications.

43. The machine-readable medium of claim 42 wherein the instructions further comprise code for comparing the copy of the notification tag received from said one of the one or more notification clients with a subsequent notification tag associated with a subsequent notification.

44. The machine-readable medium of claim 43 wherein the instructions further comprises code for discarding the subsequent notification if the copy of the notification tag received from said one of the one or more notification clients matches the subsequent notification tag.

45. The machine-readable medium of claim 36 wherein the instructions further comprise code for providing the notification to one or more other applications servers in a cluster environment.

46. The machine-readable medium of claim 36 wherein the instructions further comprise code for receiving the notification provided to the one or more notification clients from another application server in a cluster environment.

47. An application server configured to host one or more web applications and process HTTP requests associated with the one or more web applications, comprising:

means for maintaining an open HTTP connection; and

means for providing an asynchronous notification to one or more notification clients through the open HTTP connection, wherein the notification includes an identifier for the one or more notification clients with no application data payload.