Microsoft Technology Licensing, LLC

Michal Krzysztof Piaseczny

Marcus Eduardo Markiewicz

Michael John Novak

Chris J Guzak

Tyler Kien Beam

Jack Allen Nichols

Kameshwar Jayaraman

John D Fan

Jonathan Alexander Bockelman

Adam Christopher Czeisler

Juan-Lee Pang

Thottam Sriram

Amnon Itamar Govrin

Ramanathan Somasundaram

Daniel E Kogan

Jessica Anne Alspaugh

Anupama Janardhan

Bradley Stevenson

Zainal Arifin

Daniel Vincent Fiordalis

Marcelo Albuquerque Fernandes Mas

Julian Zbogar Smith

Graham Lee McMynn

Tudor Baraboi

Quentin Gary Christensen

Carlos David Argott Hernandez

Benjamin Joseph Rinaca

Jordan Spencer Rudd

Fan Mao

Amelie Dagenais

Ashish Shrikrishna Malgi

Yessen Yessetovich Amirzhanov

Benjamin M Yim

Adam David Harmetz

Matthew James Ruhlen

Ali Taleghani

Viktoriya Taranov

Hani Saliba

Patrick Miller

Michelle Elena Keslin

Chris M White

Daniel Robert Snyder

Gerhard A Schobbe

Jitesh Sachdeva

Robin A Smith

Amog Rajenderan

Dmitry Shafranov

Brian Gaiennie Hyams

Boris Isaac Feldman

Manish Soni

Nisha Tekchand Singh

Paras Pankaj Kapadia

Bowen Xue

Thottam R Sriram

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.

Enhanced co-authoring and file syncing

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.

Veto-based model for measuring product health

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.

Coordinating file synchronization between a sync engine and another application that supports document collaboration

Latency-reduced document change discovery in a co-authoring session is provided. When a co-authoring session is established between clients for co-authoring a document, a communication channel that is separate from a content channel is established between each client in the co-authoring session and a notification service. When a client uploads edits made to the document to a server-stored and managed master copy of the document, the client sends a notification on the separate channel to the other clients via the notification service, notifying the other clients that document changes have been made and are available to download from the content service. The other clients are enabled to discover document changes in real-time or in near real-time to when the changes are saved to the master copy of the document, and download the client edits for merging the changes with a local copy of the document.

Latency-reduced document change discovery

Systems and methods for enabling the real-time sharing of document edits are disclosed herein. Documents being edited may use backing stores that are not originally compatible to share edits in a coauthoring environment and thus require additional attention before coauthoring edits can be shared in real-time. The systems and methods described may provide for the analysis of high level functions within the document editor to determine the underlying activities. Both the high level functions and underlying activities may be analyzed to determine whether it is safe to implement the changes they represent in real-time on an endpoint. When it is determined that the changes are safe to implement, the changes will be implemented and further real-time edits will be shared. When it is determined that the edits are not safe to implement, real-time updates will be suspended until the next selected-time update, at which time real-time sharing will recommence.

System and method for implementing shared document edits in real-time

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.

Technologies are described herein for locating relevant content items across multiple disparate content sources. Query parameters are received from a user interface for defining a query for searching a number of content sources located on multiple, disparate content servers. A native search is executed on each of the content servers based on the received query parameters, and query statistics and other data regarding content items in the content sources matching the query parameters are received. The query statistics are aggregated across the content servers and presented in the user interface. The presentation of the query statistics may be broken out by each content source, by each query phrase segmented from the query, and the like. In addition, a preview of a number of content items matching the query parameters is presented based on the data received.

Locating relevant content items across multiple disparate content sources

Techniques to manage vocabulary terms for a taxonomy system are described. An apparatus may comprise a managed taxonomy system having a vocabulary management module to manage a taxonomy of formal vocabulary terms organized in a hierarchical structure. The taxonomy may include a category for informal vocabulary terms stored as a list of keywords. Other embodiments are described and claimed.

Techniques to manage a taxonomy system for heterogeneous resource domain

A computing device includes an operating system that manages an application and maintains threads relating thereto, where each thread has assigned attributes and the operating system executes each thread according to each attribute thereof. An interface process of the application receives a thread with a request for the application, sets an attribute of the request/thread to enforce a limitation within the application, and forwards the request/thread to the application for further processing in accordance with the limitation to produce a result. The interface process thereafter receives the same thread with the result from the application, resets the attribute of the result/thread to remove the limitation outside of the application, and forwards the result/thread for delivery to the requester. Thus, the interface process ensures by way of setting and resetting the attribute on the thread that the limitation on the application is satisfied.

Thread-based limitation on computer application

Growing community of inventors

Bellevue, WA, United States of America

Michal Krzysztof Piaseczny