Providing real time web application framework socket

• US 8,683,357 B2
• Filed: 11/25/2009
• Issued: 03/25/2014
• 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.
• Primary Examiner(s): ABDUL-ALI, OMAR R
• Application Number:
  US12/626,464
• Publication Number:
  US 20110126134A1
• Time in Patent Office: 1,581 Days
• Field of Search: 715/760, 709/232
• 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 method comprising:

receiving, by a processing device of a client device from a web application framework, a web page comprising at least one framework widget with a subscription to a topic, the at least one framework widget comprising a web application embedded in the web page;

opening, by the processing device in response to receiving the web page, a framework socket in a web browser executed by the client device to render the web page, the framework socket to enable an open communication connection between the client device and the web application framework; and

rendering the framework socket along with the at least one framework widget in the web browser.

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 in view of 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 non-transitory computer readable storage medium that provides instructions, which when executed by a processing device cause the processing device to perform operations comprising:

receiving, by the processing device of a client device from a web application framework, a web page comprising at least one framework widget with a subscription to a topic, the at least one framework widget comprising a web application embedded in the web page;

opening, by the processing device in response to receiving the web page, a framework socket in a web browser executed by the client device to render the web page, the framework socket to enable an open communication connection between the client device and the web application framework; and

rendering the framework socket along with the at least one framework widget in the web browser.

11. The non-transitory 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 non-transitory 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 non-transitory 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 non-transitory 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 non-transitory 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 non-transitory 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 non-transitory computer readable storage medium of claim 10, further comprising:

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

18. The non-transitory 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 processing device communicably coupled to the memory, the processing device to;

receive, from a web application framework, a web page comprising at least one framework widget with a subscription to a topic, the at lease one framework widget comprising a web application embedded in the web page;

open, in response to receiving the web page, a framework socket in a web browser executed by the processing device to render the web page, the framework socket to enable an open communication connection between the system and the web application framework; and

render the framework socket along with the at least one framework widget in the web browser.

20. The system of claim 19, 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.