Abstract: Techniques to perform event-based synchronization of data among a plurality of endpoints are disclosed. In various embodiments, a user interaction associated with synchronization set data that has been synchronized based on synchronization events downloaded from a synchronization server configured to propagate changes via a synchronization event stream is observed. The observed user interaction is used to infer a user preference with respect to downloaded synchronization set data. Access is provided to synchronization event related data in a subsequent download in a manner determined based at least in part on the inferred user preference.

Abstract: Techniques to synchronize data across a plurality of endpoints are disclosed. An indication that data associated with a file or other object included in a synchronization set has been changed is received from a first synchronization endpoint associated with the synchronization set. A synchronization event that reflects the change is created and added to a synchronization event stream that is accessible to a second endpoint associated with the synchronization set.

Abstract: Techniques to perform event-based synchronization of data are disclosed. In various embodiments, a synchronization is performed at a synchronization client, based at least in part on one or more synchronization events downloaded from a synchronization server. A result of said synchronization is verified at least in part by comparing a computed representation of synchronization set state as stored at the synchronization client with a corresponding computed representation of synchronization set state as stored at the synchronization server.

Abstract: Techniques to perform event-based synchronization of data are disclosed. In various embodiments, an indication is received, during the course of performing a synchronization event-based synchronization with a synchronization client, that a user of the synchronization client has provided an input associated with a request to access a file or other object the changes to which have not yet been downloaded completely to the synchronization client. Download of the changes to the file other object with respect to which the input associated with a request to access is associated is reprioritized, to enable the synchronization client to provide access to the file or other object more quickly than would have been possible without the reprioritization.

Abstract: Techniques to perform event-based synchronization of data among a plurality of endpoints are disclosed. In various embodiments, a user interaction associated with synchronization set data that has been synchronized based on synchronization events downloaded from a synchronization server configured to propagate changes via a synchronization event stream is observed. The observed user interaction is used to infer a user preference with respect to downloaded synchronization set data. Access is provided to synchronization event related data in a subsequent download in a manner determined based at least in part on the inferred user preference.

Abstract: Techniques to perform event-based synchronization of data among a plurality of endpoints are disclosed. In various embodiments, a user interaction associated with synchronization set data that has been synchronized based on synchronization events downloaded from a synchronization server configured to propagate changes via a synchronization event stream is observed. The observed user interaction is used to infer a user preference with respect to downloaded synchronization set data. Access is provided to synchronization event related data in a subsequent download in a manner determined based at least in part on the inferred user preference.

Abstract: Techniques to synchronize data across a plurality of endpoints are disclosed. An indication that data associated with a file or other object included in a synchronization set has been changed is received from a first synchronization endpoint associated with the synchronization set. A synchronization event that reflects the change is created and added to a synchronization event stream that is accessible to a second endpoint associated with the synchronization set.

Abstract: Techniques to perform event-based synchronization of data are disclosed. In various embodiments, an indication is received, during the course of performing a synchronization event-based synchronization with a synchronization client, that a user of the synchronization client has provided an input associated with a request to access a file or other object the changes to which have not yet been downloaded completely to the synchronization client. Download of the changes to the file other object with respect to which the input associated with a request to access is associated is reprioritized, to enable the synchronization client to provide access to the file or other object more quickly than would have been possible without the reprioritization.

Abstract: Techniques to synchronize data across a plurality of endpoints are disclosed. An indication that data associated with a file or other object included in a synchronization set has been changed is received from a first synchronization endpoint associated with the synchronization set. A synchronization event that reflects the change is created and added to a synchronization event stream that is accessible to a second endpoint associated with the synchronization set.

Abstract: Techniques to perform event-based synchronization of data are disclosed. In various embodiments, an indication is received, during the course of performing a synchronization event-based synchronization with a synchronization client, that a user of the synchronization client has provided an input associated with a request to access a file or other object the changes to which have not yet been downloaded completely to the synchronization client. Download of the changes to the file other object with respect to which the input associated with a request to access is associated is reprioritized, to enable the synchronization client to provide access to the file or other object more quickly than would have been possible without the reprioritization.

Abstract: Techniques to perform event-based synchronization of data are disclosed. In various embodiments, an indication is received, during the course of performing a synchronization event-based synchronization with a synchronization client, that a user of the synchronization client has provided an input associated with a request to access a file or other object the changes to which have not yet been downloaded completely to the synchronization client. Download of the changes to the file other object with respect to which the input associated with a request to access is associated is reprioritized, to enable the synchronization client to provide access to the file or other object more quickly than would have been possible without the reprioritization.