DOCUMENT SYNCHRONIZATION SOLUTION

• US 20140114912A1
• Filed: 12/30/2013
• Published: 04/24/2014
• Est. Priority Date: 02/19/2008
• Status: Active Grant

• Current Assignee: Dropbox, Inc.
• Original Assignee: International Business Machines Corporation
• Inventors: WISNESKI, David J., NAIR, Nisha K., NIRMAL, Dinesh K., TURAGA, Sandhya C.
• Granted Patent: US 9,251,236 B2
• Time in Patent Office: Days
• US Class Current: 707/608
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: G06F 16/93 Document management systems
• CPC Class Codes: G06F 16/954 Navigation, e.g. using categorised browsing
• CPC Class Codes: G06F 2216/15 Synchronised browsing
• CPC Class Codes: G06F 40/197 Version control for software G06F8/71

Abstract

A method for synchronizing a database with displayed data, includes providing a data feed to receive data from the database to provide displayed document data, detecting a database change to the data within the database by a database synchronizer to provide a change event, polling the database synchronizer using an HTTP message to detect the change event, and pushing the database change to the displayed document data to update the displayed document data in accordance with the database change and the polling. The polling includes long polling and short polling. A polling servlet within the database synchronizer performs the polling by the database synchronizer. The database synchronizer updates the displayed document data by way of a data structure. The data structure is a queue.

Claims

1. A method, comprising:

providing a data feed to receive data from an external database and a plurality of collaboration users for collaboration changes to a collaboration document, wherein the collaboration document is synchronized based on updates provided by the plurality of collaboration users and the external database;

in response to detecting a database change to a table of the external database,

translating a table name of the table to a certain feed of the data feed; and

pushing the database change to the collaboration document via the certain feed; and

in response to detecting a collaboration change made by one of the plurality of collaboration users to the collaboration document,

translating the certain feed to the table name of the table of the external database; and

pushing the collaboration change to the table of the external database.

2. The method of claim 1, further comprising:

receiving an HTTP save message from the one of the plurality of collaboration users; and

pushing the collaboration change to the external database in response to receiving the HTTP save message.

3. The method of claim 1, wherein the external database includes a database log for storing a record of the database change and further comprising:

reading the database log to detect the database change; and

creating a change event in accordance with the reading of the database log.

4. The method of claim 1, further comprising:

creating a change event in accordance with the certain feed.

5. The method of claim 1, further comprising:

polling to detect the database change, wherein the polling comprises one of long polling and short polling.

6. The method of claim 5, wherein an HTTP message remains open until one of a relevant change to the data in the external database is identified and the HTTP message times out in long polling.

7. The method of claim 6, wherein an HTTP message is generated by the one of the plurality of collaboration users and does not remain open in short polling.

8. The method of claim 1, further comprising:

polling a database synchronizer by a polling servlet of the database synchronizer.

9. The method of claim 1, further comprising:

updating the collaboration document using a data structure.

10. The method of claim 9, wherein the data structure comprises a queue.

11. The method of claim 1, wherein an external application updates the external database.

12. The method of claim 1, further comprising:

displaying the collaboration document in a browser.