ARCHITECTURE, SYSTEM AND METHOD FOR PROVIDING A REAL TIME WEB APPLICATION FRAMEWORK SOCKET

• US 20110126134A1
• 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,683,357 B2
• Time in Patent Office: Days
• US Class Current: 715/760
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

A method and apparatus for providing real-time web applications is described. In one embodiment, the method includes receiving a web page from a web application framework at a client computer system, the web page including at least one framework widget with a subscription to a topic. The method may also include opening a framework socket in a web browser run on the client computer system. In one embodiment, the method may further include rendering the framework socket along with the at least one framework widget in a web browser run by the client computer system.

Claims

1. A computer-implemented method comprising:

receiving a web page from a web application framework at a client computer system, the web page including at least one framework widget with a subscription to a topic;

opening a framework socket in a web browser run on the client computer system; and

rendering the framework socket along with the at least one framework widget in a web browser run by the client computer system.

2. The method of claim 1, wherein the framework socket is an abstraction of a transmission control protocol (TCP) socket to a web server of the web application framework created within the web browser run.

3. The method of claim 1, wherein the framework socket creates a persistent connection between the web browser run on the client computer system and the web application framework.

4. The method of claim 1, further comprising:

the framework socket determining each of framework widgets being rendered on the web page; and

automatically subscribing to a topic at the web application framework referenced by each of the determined framework widgets, the topic an abstraction of a messaging queue of the web application framework.

5. The method of claim 4, further comprising:

the framework socket connecting to a message broker via a proxy of the web application framework, the framework socket to receive data messages corresponding to widget topic subscriptions from the message broker.

6. The method of claim 1, further comprising:

the framework socket determining one or more callback functions pointed to by the at least one widget;

automatically injecting the one or more callback functions into the at least one framework widget.

7. The method of claim 6, further comprising:

executing the one or more callbacks in response to the framework socket receiving a data message for a topic to which the at least one widget subscribes.

8. The method of claim 1, further comprising:

the framework socket routing data messages to different widgets rendered within the web page based on each widgets topic subscriptions and a topic to which the data message belongs.

9. The method of claim 1, wherein a type of the framework socket is determined by a configuration file stored in the web application framework.

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

receiving a web page from a web application framework at a client computer system, the web page including at least one framework widget with a subscription to a topic;

opening a framework socket in a web browser run on the client computer system; and

rendering the framework socket along with the at least one framework widget in a web browser run by the client computer system.

11. The computer readable storage medium of claim 10, wherein the framework socket is an abstraction of a transmission control protocol (TCP) socket to a web server of the web application framework created within the web browser run on the user computer system.

12. The computer readable storage medium of claim 10, wherein the framework socket creates a persistent connection between the web browser run on the client computer system and the web application framework.

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

the framework socket determining each of framework widget being rendered on the web page; and

automatically subscribing to a topic referenced by each of the determined framework widgets, the topic an abstraction of a messaging queue of the web application framework.

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

the framework socket connecting to a message broker via a proxy of the web application framework, the framework socket to receive data messages corresponding to widget topic subscriptions from the message broker.

15. The computer readable storage medium of claim 10, further comprising:

the framework socket determining one or more callback functions pointed to by the at least one widget; and

automatically injecting the one or more callback functions into the at least one framework widget.

16. The computer readable storage medium of claim 15, further comprising:

executing the one or more callbacks in response to the framework socket receiving a data message for a topic to which the at least one widget subscribes.

17. The computer readable storage medium of claim 10, further comprising:

the framework socket routing data messages to different widgets rendered within the web page based on each widgets topic subscriptions and a topic to which the data message belongs.

18. The computer readable storage medium of claim 10, wherein a type of the framework socket is determined by a configuration file stored in the web application framework.

19. A system comprising:

a memory; and

a processor of a client computer system to

receive a web page from a web application framework at a client computer system, the web page including at least one framework widget with a subscription to a topic;

open a framework socket in a web browser run on the client computer system; and

render the framework socket along with the at least one framework widget in a web browser run by the client computer system.

20. The system of claim 20, wherein the framework socket is an abstraction of a transmission control protocol (TCP) socket to a web server of the web application framework created within the web browser run on the user computer system.