Method and system for client browser update from a lite cache

• US 20040103199A1
• Filed: 11/22/2002
• Published: 05/27/2004
• Est. Priority Date: 11/22/2002
• Status: Abandoned Application

• Current Assignee: JP Morgan Chase & Co
• Original Assignee: JP Morgan Chase & Co
• Inventors: Chao, Anthony, Graham, Mark
• Application Number:
  US10/065,817
• Publication Number:
  US 20040103199A1
• Time in Patent Office: Days
• US Class Current: 709/228
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching

Abstract

A method and system for data cache with browser notification of a change in the cache and update of the browser information content from the cache. A subset of data in a larger SQL type database, in the form of a lite cache is extracted and stored in RAM. The lite cache includes a record ID and one variable, although the SQL type database typically includes a plurality of variables associated with the record ID. The lite cache is updated on a periodic basis from the SQL type database. A client browser establishes an HTTP connection with a server and loads a web page with information content including content from the lite cache. The server and client also establish a TCP socket connection to pass messages from the server to the client over the socket connection. When the lite cache is updated and it is determined that browser content from the lite cache needs update or has changed, the application server triggers transmission of a change notice message over the socket connection. Upon browser receipt of the change notice message, the browser initiates a refresh of the information content over the HTTP connection.

Claims

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

creating a data cache as a subset of a larger database;

performing a periodic refresh of the data cache from the larger database;

identifying change in the data cache;

responsive to the change in the data cache, sending a message to the client; and

responsive to the message, automatically requesting the changed data.

2. A method according to claim 1, further comprising:

establishing a connection between the client and a server; and

responsive to a request from the client to the server, sending a set of data from the data cache to the client.

3. A method according to claim 2, wherein the connection uses HTTP protocol.

4. A method according to claim 1, further comprising:

establishing a connection between the client and a server; and

sending the message to the client from the server using the connection.

5. A method according to claim 4, wherein the connection uses TCP protocol.

6. A method according to claim 1, further comprising:

establishing a first connection between the client and a server;

establishing a second connection between the client and the server;

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

sending the message to the client from the server using the second connection; and

responsive to the message, automatically sending the request for the changed data from the client to the server using the first connection.

7. A method according to claim 1, wherein the message has at least two states, one state indicating no change in the data cache, and the other state indicating change in the data cache.

8. A method according to claim 7, wherein requesting the changed date is responsive to the message state indicating change in the data cache.

9. A method according to claim 1, wherein the message is periodic.

10. A method according to claim 1, wherein the message is aperiodic.

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

creating a data cache in a RAM cache of an application server as a subset of a larger database;

establishing an HTTP connection between the client and the application server;

establishing a TCP connection between the client and the application server;

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

after the first time, performing a periodic refresh of the data cache from the larger database;

identifying change in the data cache;

responsive to the change in the data cache, sending a message from the application server to the client via the TCP connection; and

responsive to the message, sending a request for the changed data from the client to the application server via the HTTP connection.

12. Computer executable software code transmitted as an information signal, the code for updating information on a client computer, the code comprising:

code to create a data cache as a subset of a larger database;

code to perform a periodic refresh of the data cache from the larger database;

code to identify change in the data cache;

responsive to the change in the data cache, code to send a message to the client; and

responsive to the message, code to automatically request the changed data.

13. A computer readable medium having computer executable code stored thereon, the code for updating information on a client computer, the code comprising:

code to create a data cache as a subset of a larger database;

code to perform a periodic refresh of the data cache from the larger database;

code to identify change in the data cache;

responsive to the change in the data cache, code to send a message to the client; and

responsive to the message, code to automatically request the changed data.

14. A programmed computer for updating information on a client 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 create a data cache as a subset of a larger database;

code to perform a periodic refresh of the data cache from the larger database;

code to identify change in the data cache;

responsive to the change in the data cache, code to send a message to the client; and

responsive to the message, code to automatically request the changed data.