DOCUMENT SYNCHRONIZATION SOLUTION

• US 20090210459A1
• Filed: 02/19/2008
• Published: 08/20/2009
• Est. Priority Date: 02/19/2008
• Status: Active Grant

• Current Assignee: Dropbox, Inc.
• Original Assignee: International Business Machines Corporation
• Inventors: Nair, Nisha K., Turaga, Sandhya C., Nirmal, Dinesh, Wisneski, David J.
• Granted Patent: US 8,650,154 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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 for synchronizing a database with displayed data, comprising:

providing a data feed to receive data from said database and provide displayed document data;

detecting a database change to said data within said database by a database synchronizer to provide a change event;

polling said database synchronizer using an HTTP message to detect said change event; and

pushing said database change to said displayed document data to update said displayed document data in accordance with said database change and said polling.

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

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

4. The method for synchronizing a database of claim 1, further comprising polling said database synchronizer by a polling servlet of said database synchronizer.

5. The method for synchronizing a database of claim 2, further comprising updating said displayed document data by way of a data structure.

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

7. The method for synchronizing a database of claim 2, further comprising:

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

collaboration synchronizing said display document data to provide a synchronized collaboration document wherein said synchronized collaboration document displays said collaboration changes of said plurality of collaboration changes.

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

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

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

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

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

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

collaboration synchronizing said display document data 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 pushing data of said synchronized collaboration document to said database.

14. The method for synchronizing a database of claim 13, 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.

15. The method for synchronizing a database of claim 1, wherein said database includes a database log for storing a record of said database change further comprising:

reading said database log to detect said database change; and

creating said change event in accordance with said reading of said database log.

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

17. A method for synchronizing a database with a collaboration document wherein a plurality of collaborating users make a plurality of collaboration changes to said collaboration document, comprising:

determining a collaboration change of said plurality of collaboration changes using an HTTP message to provide a determined collaboration change;

pushing said determined collaboration change to said database;

synchronizing said plurality of collaboration changes to provide a synchronized collaboration document;

polling a database synchronizer to detect a database change to said data within said database to provide a change event; and

pushing said change event to said synchronized collaboration document by said database synchronizer.

18. The method for synchronizing a database of claim 17, further comprising pushing said determined collaboration change by way of said database synchronizer.

19. The method for synchronizing a database of claim 18, further comprising pushing said change event by way of a data structure.

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