Client side caching of synchronized data

• US 8,725,679 B2
• Filed: 04/07/2008
• Issued: 05/13/2014
• Est. Priority Date: 04/07/2008
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Nair, Nisha K., Nirmal, Dinesh, Turaga, Sandhya C., Wisneski, David J.
• Primary Examiner(s): PHILLIPS, III, ALBERT M
• Application Number:
  US12/098,706
• Publication Number:
  US 20090254589A1
• Time in Patent Office: 2,227 Days
• Field of Search: 707/999.01, 707/610, 707/631, 707/628, 707/635, 707/608, 707/612, 709/203, 709/223, 709/202, 709/227, 705/4, 717/101
• US Class Current: 707/608
• CPC Class Codes: G06F 16/275 Synchronous replication

Abstract

A method for synchronizing a database with data stored at a client includes providing a data feed to receive data by the client from the database and provide received data, caching the received data in a client side cache to provide client side cached data, detecting a database change to data within the database corresponding to the client side cached data according to a polling operation to provide a change event, pushing the change event to the client side cached data to update the client side cached data in accordance with the database change and the polling operation, requesting further data from the database, determining whether the further data includes data of the client side cached data to determine remaining data exclusive of the client side cached data and pushing the remaining data to the client side cached data.

Claims

1. A method for synchronizing a database with data stored at clients, comprising:

receiving a collaboration change to a collaboration document from a collaboration user from among a plurality of collaboration users in multiple collaboration groups at said clients;

caching said collaboration change in a client side cache to provide client side cached data at said client;

pushing said cached data to update said collaboration document displayed to said plurality of collaboration users, wherein said collaboration document is a synchronized collaboration document that is synchronized based on any updates provided by said plurality of collaboration users and said database;

saving said collaboration change from said cached data in said database;

receiving by said database a first, new database change from an external application that is external to said database and to said client while said plurality of collaboration users are collaborating on said collaboration document, wherein said database, said collaboration document, and said external application are separate, and wherein said external application provides a second new database change while said collaboration users are not collaborating on said collaboration document;

pushing said second, new database change to a set of client event queues for said plurality of collaboration users in said multiple collaboration groups at said clients, wherein said second, new database change is saved as a single instance within said set of client event queues, and wherein a reference of said single instance is provided to each of said client event queues in said set of client event queues;

pushing said second, new database change to said plurality of collaboration users in said multiple collaboration groups at said clients; and

in response to said pushing, deleting said single instance.

2. The method for synchronizing a database of claim 1, further comprising detecting said new database change in accordance with a long polling operation.

3. The method for synchronizing a database of claim 1, further comprising detecting said new database change in accordance with a short polling operation.

4. The method for synchronizing a database of claim 1, wherein said determining whether said further data includes data of said client side cached data comprises determining by a cache handler servlet.

5. The method for synchronizing a database of claim 4, further comprising determining whether data includes said client side cached data according to key/value pairs of said client side cached data.

6. The method of synchronizing a database of claim 1, said database includes summary data and associated detail data and wherein said received data comprises received summary data.

7. The method for synchronizing a database of claim 6, wherein said further data comprises detail data associated with said received summary data.

8. The method for synchronizing a database of claim 1, further comprising pushing a change event to said client side cached data.

9. The method for synchronizing a database of claim 8, further comprising polling to detect said new database change said synchronizer server by a polling servlet of said synchronizer server.

10. The method for synchronizing a database of claim 9, further comprising updating said client side cached data by way of a data structure.

11. The method for synchronizing a database of claim 10, wherein said data structure comprises a queue.

12. The method for synchronizing a database of claim 1, further comprising displaying said displayed collaboration document in a browser.

13. The method for synchronizing a database of claim 12, further comprising:

providing an HTTP save message by a collaboration user of said one or more collaboration users; and

pushing said data of said collaboration document in response to said HTTP save message.

14. The method for synchronizing a database of claim 13, further comprising creating a change event in accordance with a feedname of said displayed collaboration document.

15. The method for synchronizing a database of claim 1, further comprising providing a data feed by said client to receive data from said database and provide received data, wherein a feedname corresponds to a table in said database.