Method and system for client browser update

• US 7,987,246 B2
• Filed: 05/23/2002
• Issued: 07/26/2011
• Est. Priority Date: 05/23/2002
• Status: Active Grant

• Current Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Original Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Inventors: Grinshteyn, Mikhail, Tsuji, Michael, Wong, Hok Yee, Minocha, Nikhil
• Primary Examiner(s): Joo; Joshua
• Application Number:
  US10/154,129
• Publication Number:
  US 20030220989A1
• Time in Patent Office: 3,351 Days
• Field of Search: 709203-204, 709/217, 709/220
• US Class Current: 709/220
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching

Abstract

A method and system for browser notification of a change in browser information content and update of the browser information content. A browser establishes an http connection with a server and loads a web page with information content. At the same time, the server and client also establish a socket connection to pass messages from the server to the client over the socket connection. When the server determines that browser content needs update or has changed, the server sends a change notice message over the socket connection. Upon browser receipt of the change notice message, the browser initiates an refreshes the information content over the http connection.

Claims

1. A method for changing information on a computer, the method comprising:

establishing a first connection between a client and a first server;

responsive to a request from the client to the first server, sending a set of data to the client;

establishing a second connection between the client and a second server;

the first server receiving a notification of a change in the set of data;

sending a regularly repeating heartbeat message from the second server to the client over the second connection; and

responsive to a change in content of the heartbeat message, automatically sending a request from the client to the first server over the first connection for a change in the set of data;

wherein the heartbeat message has two states, one state indicating no change in the set of data, and the other state indicating change in the set of data.

2. The method according to claim 1, wherein the first connection uses http protocol.

3. The method according to claim 1, wherein the second connection uses TCP protocol.

4. The method according to claim 1, wherein sending the request for a change is responsive to a state of the heartbeat message indicating change in the set of data.

5. The method according to claim 1, wherein the first server and the second server are parts of a single server.

6. The method according to claim 1, wherein the set of data includes data formatted as html.

7. The method according to claim 6, wherein the html of the set of data includes code for a visible frame and code for an invisible frame.

8. The method of claim 1, wherein the client is a browser.

9. A method for notifying a client browser of a change in a set of data, the method comprising:

establishing an http connection between the client browser and an application server;

establishing a TCP connection between the client browser and a notification server;

the application server receiving a notification of a change in the set of data;

transmitting a regularly repeating heartbeat message from the notification server to the client browser using the TCP connection;

responsive to a resource request from the client browser, sending an html file via the http connection to the client browser, the html file reflecting data at a first time;

responsive to a change in the set of data after the first time, changing content of the heartbeat message; and

responsive to the change in the content of the heartbeat message, sending a request from the client browser to the application server via the http connection for the changed data;

wherein the heartbeat message has two states, one state indicating no change in the set of data, and the other state indicating change in the set of data.

10. A non-transitory computer readable storage medium having computer executable code stored thereon, the code for changing information on a client computer, the code comprising:

code to establish a first connection between a client and a first server;

responsive to a request from the client to the first sever, code to send a set of data to the client;

code to establish a second connection between the client and a second server;

code for the first server to receive a notification of a change in the set of data;

code to send a regularly repeating heartbeat message from the second server to the client over the second connection; and

responsive to a change in content of the heartbeat message, code to automatically send a request from the client to the first server over the first connection for a change in the set of data;

wherein the heartbeat message has two states, one state indicating no change in the set of data, and the other state indicating change in the set of data.

11. A programmed computer for changing information on a computer, comprising:

a memory having at least one region for storing computer executable program code; and

a processor for executing the program code stored in the memory, wherein the program code comprises;

code to establish a first connection between a client and a first server;

responsive to a request from the client to the first sever, code to send a set of data to the client;

code to establish a second connection between the client and a second server;

code for the first server to receive a notification of a change in the set of data;

code to send a regularly repeating heartbeat message from the second server to the client over the second connection; and

responsive to a change in content of the heartbeat message, code to automatically send a request from the client to the first server over the first connection for a change in the set of data;

wherein the heartbeat message has two states, one state indicating no change in the set of data, and the other state indicating change in the set of data.

12. A method for updating a client browser with information, the method comprising:

establishing a first connection between the client browser and a first server using a http protocol;

responsive to a request from the client browser to the first server, sending a set of data to the client browser;

establishing a second connection between the client browser and a second server using a TCP protocol;

the first server receiving a notification of a change in the set of data;

sending a regularly repeating heartbeat message from the second server to the client browser over the second connection, the heartbeat message having two states, one state indicating no change in the set of data, and the other state indicating change in the set of data; and

responsive to the heartbeat message indicating a change in content in the set of data, automatically sending a request from the client browser to the first server over the first connection for a change in the set of data.