METHOD AND APPARATUS FOR ENHANCED SYNCHRONIZATION PROTOCOL

• US 20090113412A1
• Filed: 10/29/2007
• Published: 04/30/2009
• Est. Priority Date: 10/29/2007
• Status: Abandoned Application

• Current Assignee: Sap Portals Israel Ltd (SAP SE)
• Original Assignee: Sap Portals Israel Ltd (SAP SE)
• Inventors: SHRIBMAN, Aidan, DROBINSKY, Alexander
• Application Number:
  US11/926,170
• Publication Number:
  US 20090113412A1
• Time in Patent Office: Days
• US Class Current: 717/170
• CPC Class Codes: G06F 16/10 File systems; File servers

Abstract

A method and apparatus for synchronizing a file between a sender and a receiver. The sender comprises a base version of the file and optionally one or more delta files. The receiver issues a request to get updates for the file and indicates a unique ID associated with the version available at the receiver. The sender determines the version available to the receiver, and updates the receiver with all delta files accumulated since the receiver received the last update of the file. If the version of the receiver is older than the base version, then the base version and all delta files are sent to the receiver.

Claims

1. In a computerized network comprising a sender computing platform and a receiver computing platform, a method for synchronizing an at least one file between the sender computing platform and the receiver computing platform, the method comprising:

storing an at least one base version for the at least one file at the sender;

storing a collection comprising an at least one delta file associated with the at least one file at the sender;

determining a version of the at least one file available at the receiver;

sending an at least one full version of the at least one file or an at least one delta file; and

updating the at least one base version at the receiver computing platform, or applying the at least one delta file to a previous version at the receiver computing platform.

2. The method of claim 1 further comprising the step of sending a request from the receiver computing platform to the sender computing platform, the request indicating the at least one file to be synchronized and an at least one identifier associated with the file.

3. The method of claim 1 further comprising the step of determining a unique ID for the base version of the at least one file.

4. The method of claim 3 further comprising the step of determining a unique ID for a version of the at least one file, the version of the at least one file comprising the base version of the at least one file, at which the at least one delta file is applied.

5. The method of claim 1 wherein the at least one delta file sent to the receiver comprises all delta files that have been stored at the sender computing platform after all earlier delta files were sent to the receiver computing platform.

6. The method of claim 1 wherein the full version is the base version.

7. The method of claim 1 wherein the full version is generated by applying the at least one delta files on the base version.

8. The method of claim 7 wherein the full version is cached by the sender.

9. The method of claim 1 further comprising the step of issuing an at least one notification from the sender computing platform to the receiver computing platform related to an at least one updated file.

10. The method of claim 1 further comprising the step of determining an at least one identifier associated with a version of the at least one file stored at the receiver computing platform.

11. The method of claim 1 further comprising the steps of:

evicting the at least one base version and the at least one delta file; and

storing an updated base version of the at least one file.

12. An apparatus for synchronizing an at least one file between a sender computing

platform and a receiver computing platform,

the sender computing platform comprising:

a storage unit for storing an at least one base version for the at least one file and an at least one delta file for the at least one file;

a synchronization manager for determining whether the at least one file needs to be updated;

a repository revision manager for managing the at least one base version and the at least one delta file;

a cache aging determination component for determining whether to evict the at least one base version and the at least one delta file;

a file unique ID determination component for determining a unique ID of the at least one base version or a unique ID of the base version at which the at least one delta file was applied;

a communication component for sending files to the receiver;

the receiver computing platform comprising;

a storage unit for storing the at least one base version for the at least one file or an at least one delta file for the at least one file;

or an at least one base version at which an at least one delta file was applied;

a delta application component for applying an at least one delta files to a stored version of the at least one file; and

a communication component for receiving files from the receiver.

13. The apparatus of claim 12 wherein the receiver further comprises a synchronization manager for issuing an update request to the sender related to the at least one file.

14. The apparatus of claim 12 wherein the receiver further comprises a file unique ID determination component for determining a unique ID of the at least one base version, or a unique ID of the at least one base version at which the at least one delta file is applied.

15. The apparatus of claim 12 wherein the sender further comprises a delta determination component for determining a delta file between two versions of a file.