ARCHITECTURE, SYSTEM AND METHOD FOR A MESSAGING HUB IN A REAL-TIME WEB APPLICATION FRAMEWORK

• US 20110125823A1
• Filed: 11/25/2009
• Published: 05/26/2011
• Est. Priority Date: 11/25/2009
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Macken, Luke J.
• Granted Patent: US 8,301,718 B2
• Time in Patent Office: Days
• US Class Current: 709/201
• CPC Class Codes: G06F 2209/545 Gui
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

A method and apparatus for providing a hub in a real-time web application framework is described. In one embodiment, the method includes running applications on a hub server computer system within a real-time web application framework. The method may also include running each application based on configuration parameters associated with each application, the hub server computer system running the applications outside of a web application stack run on a web server computer system of the real-time web application framework.

Claims

1. A computer implemented method:

running applications on a hub server computer system within a real-time web application framework; and

running each application based on configuration parameters associated with each application, the hub server computer system running the applications outside of a web application stack run on a web server computer system of the real-time web application framework.

2. The method of claim 1, wherein the applications are plug-in applications installed on entry points of the hub.

3. The method of claim 1, wherein the hub executes the applications in conjunction with a web application stack executed by the web server, the hub server computer system operates independent of the web server.

4. The method of claim 1, wherein running each application further comprises:

waking each application on a periodic basis, the periodic basis defined by application configuration parameters;

running the application to obtain data; and

storing the obtained data in a database or cache memory accessible to a web server.

5. The method of claim 1, wherein running each application further comprises:

waking each application on a periodic basis, the periodic basis defined by application configuration parameters;

running the application to obtain data; and

transmitting the obtained data to a message broker, wherein the message broker is to route the obtained data to a destination.

6. The method of claim 5, further comprising:

translating the obtained data to a format appropriate for a particular message broker; and

routing the translated data to the particular message broker for delivery to at least one framework widget rendered in a client.

7. The method of claim 1, wherein each application is associated with a topic, the topic an abstraction of one a plurality of messaging queues implemented by the message broker.

8. The method of claim 1, wherein one of the applications is a producer application, the producer application to acquire data from a source over a network and send the acquired data to a message queue managed by a message broker.

9. A computer readable storage medium that provides instructions, which when executed on a processing system cause the processing system to perform a method comprising:

running applications on a hub server computer system within a real-time web application framework; and

running each application based on configuration parameters associated with each application, the hub server computer system running the applications outside of a web application stack run on a web server computer system of the real-time web application framework.

10. The computer readable storage medium of claim 9, wherein the applications are plug-in applications installed on entry points of the hub.

11. The computer readable storage medium of claim 9, wherein the hub executes the applications in conjunction with the web application stack executed by the web server, the hub server computer system operates independent of the web server.

12. The computer readable storage medium of claim 9, wherein running each application further comprises:

waking each application on a periodic basis, the periodic basis defined by application configuration parameters;

running the application to obtain data; and

storing the obtained data in a database or cache memory accessible to a web server.

13. The computer readable storage medium of claim 9, wherein running each application further comprises:

waking each application on a periodic basis, the periodic basis defined by application configuration parameters;

running the application to obtain data; and

transmitting the obtained data to a message broker, wherein the message broker is to route the obtained data to a destination.

14. The computer readable storage medium of claim 13, further comprising:

translating the obtained data to a format appropriate for a particular message broker; and

routing the translated data to the particular message broker for delivery to at least one framework widget rendered in a client.

15. The computer readable storage medium of claim 9, wherein each application is associated with a topic, the topic an abstraction of one a plurality of messaging queues implemented by the message broker.

16. The computer readable storage medium of claim 9, wherein one of the applications is a producer application, the producer application to acquire data from a source over a network and send the acquired data to a message queue managed by a message broker.

17. A system comprising:

a memory to store applications; and

a processor coupled with the memory to;

run applications on a hub server computer system within a real-time web application framework; and

run each application based on configuration parameters associated with each application, the hub server computer system running the applications outside of a web application stack run on a web server computer system of the real-time web application framework.

18. The system of claim 17, wherein the processor is further to wake each application on a periodic basis, the periodic basis defined by application configuration parameters, run the application to obtain data, and transmit the obtained data to a message broker, wherein the message broker is to route the obtained data to a destination.

19. The system of claim 18, wherein the processor is further to translate the obtained data to a format appropriate for a particular message broker, and route the translated data to the particular message broker for delivery to at least one framework widget rendered in a client.

20. The system of claim 17, wherein the hub executes the applications in conjunction with the web application stack executed by the web server.