Bi-directional data modification with synchronization

• US 7,831,558 B2
• Filed: 06/22/2007
• Issued: 11/09/2010
• Est. Priority Date: 06/22/2007
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Ozzie, Jack E, Moromisato, George P, Sagar, Akash J, Suthar, Paresh S, Ozzie, Raymond E, Chung, Richard Yiu-Sai, Augustine, Matthew S
• Primary Examiner(s): Trujillo; James
• Assistant Examiner(s): Spieler; William
• Application Number:
  US11/767,001
• Publication Number:
  US 20080320055A1
• Time in Patent Office: 1,236 Days
• Field of Search: 707/610, 707/626, 707/635, 707/809
• US Class Current: 707/626
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Abstract

Systems and methods for synchronizing data between endpoints, including the modification of data on an endpoint without necessarily modifying data that is communicated between endpoints are disclosed. In such systems and methods the representation of data on an endpoint may be modified so that constraints on that particular endpoint are enforced, without requiring a similar or the same modification to the data when it is synchronized to other endpoints.

Claims

1. A method, comprising:

storing a local domain data item, the local domain data item being stored compatibly with local constraints for representing the local domain data item;

receiving, from a first remote endpoint, first synchronization data reflecting a first update to a remote domain data item that is stored at the first remote endpoint;

determining whether applying the first update to the local domain data item is incompatible with the local constraints; and

when applying the first update is incompatible with the local constraints;

identifying a modification to the local domain data item that implements the first update compatibly with the local constraints;

realizing the first synchronization data on the local domain data item by applying the modification to the local domain data item;

after the realizing, applying a locally generated second update to the local domain data;

generating second synchronization data reflecting the first update and the second update, but not the modification; and

sending the second synchronization data to a second remote endpoint.

2. The method of claim 1 wherein the first synchronization data is consistent with a protocol defining extensions relating to synchronizing data using a feed.

3. The method of claim 1 wherein the local constraints identify characters that are supported in the first synchronization data but that are not supported in the local domain data item, and the modification comprises replacing an unsupported character in the first synchronization data with a character that is supported in the local domain data item.

4. The method of claim 1 wherein the remote domain data item and the local domain data item are file system elements.

5. The method of claim 4 wherein the local constraints relate to:

a duplicate file system element;

a cycle involving the local domain data item; and

an orphaned local domain data item.

6. The method of claim 1 wherein the modification further comprises:

storing the local domain data item in a location that is different from a location specified by the first update.

7. The method of claim 1 further comprising:

recording in a tabular data structure an identifier associated with the first update and, associated with the identifier, recording the description of the modification to the local domain data item.

8. The method of claim 1 further comprising:

prior to realizing the first synchronization data on the local domain data, merging the first synchronization data with additional synchronization data reflecting at least one additional update to the local domain data,

wherein the merging comprises;

determining whether the first synchronization data is associated with the additional synchronization data by evaluating whether the first synchronization data and the additional synchronization data are associated with the same identifier;

determining whether the additional synchronization data should be updated when the first synchronization data is associated with the additional synchronization data by choosing a winning synchronization data and a losing synchronization data from the first synchronization data and the additional synchronization data by comparing the first synchronization data and the additional synchronization data; and

updating the local domain data item based on the winning synchronization data.

9. The method of claim 8 wherein the winning synchronization data is determined based on at least one of the following comparisons:

comparing item version attributes of the first synchronization data and the additional synchronization data, where a larger version attribute value is associated with the winning synchronization data;

comparing item modification time attributes of the first synchronization data and the additional synchronization data, where a later modification time attribute value is associated with the winning synchronization data; and

comparing modifying entity attributes of the first synchronization data and the additional synchronization data, where a greater modifying entity value is associated with the winning synchronization data.

10. A system comprising:

a first endpoint configured to store first domain data;

a second endpoint configured to store second domain data, the second domain data being stored compatibly with constraints particular to the second endpoint; and

a third endpoint configured to store third domain data;

the first endpoint being further configured to;

apply a first update to the first domain data, wherein the first update is at least partially incompatible with the constraints particular to the second endpoint;

generate first synchronization data reflecting the first update to the first domain data; and

send the first synchronization data to the second endpoint;

the second endpoint being further configured to;

identify a modification to the second domain data that implements the first update compatibly with the constraints particular to the second endpoint;

apply the modification to the second domain data;

apply a second update to the second domain data, the second update being compatible with the constraints particular to the second endpoint;

generate second synchronization data reflecting the first update and the second update, but not the modification; and

send the second synchronization data to the third endpoint; and

the third endpoint being further configured to;

receive the second synchronization data from the second endpoint; and

based on the second synchronization data, apply the first update and the second update to the third domain data independently of the constraints particular to the second endpoint.

11. A method, comprising:

identifying a locally stored domain data item stored compatibly with a local constraint;

determining whether the locally stored domain data item was previously modified to be compatible with the local constraint as part of realizing first synchronization data received from a first remote endpoint on to the locally stored domain data item; and

when the locally stored domain data item was previously modified to be compatible with the local constraint;

recording a description of how the locally stored domain data item was modified to be compatible with the local constraint;

generating second synchronization data using the description of how the locally stored domain data item was modified, wherein the second synchronization data reflects the first synchronization data as received from the first remote endpoint, independently of how the locally stored domain data item was modified to be compatible with the local constraint; and

sending the second synchronization data to a second remote endpoint.

12. The method of claim 11 wherein the first synchronization data is consistent with a protocol defining extensions relating to synchronizing data using a feed.

13. The method of claim 11 wherein at least a portion of the first synchronization data is not included in the locally stored domain data item.

14. The method of claim 11 wherein the locally stored domain data item is a file system element and the first synchronization data includes file system information associated with the file system element.

15. The method of claim 11, further comprising:

before generating the second synchronization data, updating the locally stored domain data item to include new information; and

including the new information in the second synchronization data.

16. The method of claim 15 wherein the second synchronization data further comprises a second feed item that includes a feed sync data element and an item data element corresponding to the locally stored domain data item, and further comprising:

modifying item data associated with the item data element so that the item data includes at least a portion of the new information;

incrementing a version value associated with the feed sync data element;

creating a new update element associated with the feed sync data element and further associated with at least one of;

a previous most recent modification time and a previous most recent modifying entity; and

updating at least one of;

a most recent modification time history attribute associated with the feed sync data element and a most recent modifying entity history attribute associated with the feed sync data element.