CLIENT SIDE CACHING OF SYNCHRONIZED DATA

• US 20090254589A1
• Filed: 04/07/2008
• Published: 10/08/2009
• Est. Priority Date: 04/07/2008
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Wisneski, David J., Nair, Nisha K., Turaga, Sandhya C., Nirmal, Dinesh
• Granted Patent: US 8,725,679 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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 a client, comprising:

providing a data feed to receive data by said client from said database and provide received data;

caching said received data in a client side cache to provide client side cached data;

detecting a database change to data within said database corresponding to said client side cached data according to a polling operation to provide a change event;

pushing said change event to said client side cached data to update said client side cached data in accordance with said database change and said polling operation;

requesting further data from said database;

determining whether said further data includes data of said client side cached data to determine remaining data exclusive of said client side cached data; and

pushing said remaining data to said client side cached data.

2. The method for synchronizing a database of claim 1, wherein said polling operation comprises a long polling operation.

3. The method for synchronizing a database of claim 1, wherein said polling operation comprises a short polling operation.

4. The method for synchronizing a database of claim 2, 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 said further 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 4, wherein said received data comprises summary data.

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

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

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

providing displayed document data according to said client side cached data;

changing said displayed document data by a plurality of collaboration users to provide a plurality of collaboration changes; and

collaboration synchronizing said displayed document data by said client to provide a synchronized collaboration document wherein said synchronized collaboration document displays said collaboration changes of said plurality of collaboration changes.

13. The method for synchronizing a database of claim 12, further comprising synchronizing said displayed document data by a GOOGLE application program.

14. The method for synchronizing a database of claim 13, further comprising caching said received data in a JSOC.

15. The method for synchronizing a database of claim 14, further comprising representing said data in said JSOC using a JSON string.

16. The method for synchronizing a database of claim 13, wherein said GOOGLE application program comprises a spreadsheet application program.

17. The method for synchronizing a database of claim 12, further comprising pushing data of said synchronized collaboration document to said database.

18. The method for synchronizing a database of claim 17, further comprising displaying said displayed document data in a browser.

19. The method for synchronizing a database of claim 18, further comprising:

providing an HTTP save message by a collaboration user of said plurality of collaboration users; and

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

20. The method for synchronizing a database of claim 19, further comprising creating said change event in accordance with a feedname of said displayed document data.

9. The method for synchronizing a database of claim 9, further comprising polling 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.