×

Conflict management during data object synchronization between client and server

  • US 7,529,780 B1
  • Filed: 12/30/2005
  • Issued: 05/05/2009
  • Est. Priority Date: 12/30/2005
  • Status: Active Grant
First Claim
Patent Images

1. A computer implemented method for synchronizing data objects stored on a server and a client, comprising:

  • at the server, storing server metadata entries corresponding to a plurality of data objects, wherein each server metadata entry associates both an identifier and a server file name, distinct from the identifier, with a respective data object, the server file name including a directory path;

    at the server;

    during a first phase of a synchronization process, receiving one or more client metadata entries from the client, each of the client metadata entries corresponding to a data object for which at least one metadata parameter has changed since a prior execution of the synchronization process, wherein each client metadata entry associates both an identifier and a client file name, distinct from the identifier, with a respective data object, the client file name including a directory path;

    during the first phase of the synchronization process, rejecting any received client metadata entry that contains one or more updated metadata parameters that conflict with metadata parameters of a corresponding server metadata entry, and accepting any received client metadata entry that does not conflict with a corresponding server metadata entry, wherein a server metadata entry corresponds to a received client metadata entry when the received client metadata entry contains a same identifier as the server metadata entry without regard to whether the server file name and client file name of the server metadata entry and client metadata entry match;

    during a second phase of the synchronization process, sending to the client one or more server metadata entries, each of the server metadata entries corresponding to a data object for which at least one metadata parameter has changed since a prior execution of the synchronization process;

    wherein, when a client metadata entry has been rejected at the server during the first phase, the one or more server metadata entries sent to the client include at least one server metadata entry that conflicts with the rejected client metadata entry; and

    during a subsequent phase of the synchronization process, performing a content update operation comprising at least one of a content upload operation and a content download operation;

    the content upload operation comprising uploading to the client one or more server content updates, each of the server content updates corresponding to a data object for which at least one content parameter has changed since a prior execution of the synchronization process;

    wherein the one or more server content updates uploaded to the client are associated with the one or more server metadata entries sent to the client during the second phase of the synchronization process;

    the content download operation comprising downloading from the client one or more client content updates, each of the client content updates corresponding to a data object for which at least one content parameter has changed since a prior execution of the synchronization process;

    wherein the one or more client content updates downloaded from the client are associated with the one or more client metadata entries received from the client during the first phase of the synchronization process.

View all claims
  • 2 Assignments
Timeline View
Assignment View
    ×
    ×