Abstract: In an implementation, a sync engine running on a computing device synchronizes a local copy of a file with a copy of the file hosted by an online file service. An application on the device receives a request/command to open the file and responsively opens a temporary copy of the file in memory. The application populates the temporary file with content from the local copy of the file and also establishes a connection between the application and a co-authoring service. Note that the connection between the application and the co-authoring session bypasses the sync engine such, when connected to the co-authoring service, the application is able to synchronize the content in the temporary copy of the file with content in the hosted copy of the file over the connection.

Abstract: The performance of a cloud-based software product over time is determined by collecting telemetry data representing whether different features of online sessions of the software product are operating properly. The telemetry data represents shared performance metrics of the software product across different participants and components participating in an online session. The collected telemetry data is correlated with session identifiers identifying the online session from which the telemetry data was collected. The telemetry data for an online session is processed to establish a unit of failure when the telemetry data indicates that the online session operated outside of predefined performance metrics. The unit of failure is a function of vetoes applied to a candidate list of online sessions indicating that the online session may have problems. The performance of the software product may be determined as a function of the unit of failure over time.

Abstract: A computing system includes at least one processor and memory storing instructions executable by the at least one processor, wherein the instructions, when executed, cause the computing system to instruct a synchronization engine to synchronize first and second versions of a file, the first version being stored on a first storage system and the second version being stored on a second storage system, receive a backoff indicator corresponding to the file, based on the backoff indicator, instruct the synchronization engine to backoff synchronizing changes to the file, and allow the changes to the file to be synchronized by a co-authoring application, maintain a first set of collaborative metadata indicative of content of the first version of the file, and maintain a second set of collaborative metadata indicative of content of the second version of the file.

Abstract: The performance of a cloud-based software product over time is determined by collecting telemetry data representing whether different features of online sessions of the software product are operating properly. The telemetry data represents shared performance metrics of the software product across different participants and components participating in an online session. The collected telemetry data is correlated with session identifiers identifying the online session from which the telemetry data was collected. The telemetry data for an online session is processed to establish a unit of failure when the telemetry data indicates that the online session operated outside of predefined performance metrics. The unit of failure is a function of vetoes applied to a candidate list of online sessions indicating that the online session may have problems. The performance of the software product may be determined as a function of the unit of failure over time.

Abstract: A computing system includes at least one processor and memory storing instructions executable by the at least one processor, wherein the instructions, when executed, cause the computing system to instruct a synchronization engine to synchronize first and second versions of a file, the first version being stored on a first storage system and the second version being stored on a second storage system, receive a backoff indicator corresponding to the file, based on the backoff indicator, instruct the synchronization engine to backoff synchronizing changes to the file, and allow the changes to the file to be synchronized by a co-authoring application, maintain a first set of collaborative metadata indicative of content of the first version of the file, and maintain a second set of collaborative metadata indicative of content of the second version of the file.

Abstract: A synchronization engine detects a notification of a change to a file. It determines whether an application associated with the file has indicated that the file is to be synchronized by the application. If so, the changes to the file are synchronized between a cloud-based storage system and a local disk by the application. Collaborative metadata, associated with the synchronized file, is updated to indicate a state of a copy of the file on the local disk and a copy of the file in the cloud-based storage system. The collaborative metadata is stored by the synchronization engine.

Abstract: A synchronization engine detects a notification of a change to a file. It determines whether an application associated with the file has indicated that the file is to be synchronized by the application. If so, the changes to the file are synchronized between a cloud-based storage system and a local disk by the application. Collaborative metadata, associated with the synchronized file, is updated to indicate a state of a copy of the file on the local disk and a copy of the file in the cloud-based storage system. The collaborative metadata is stored by the synchronization engine.