Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: A computer system supports measuring execution time of concurrent threads. A thread allocates a timing buffer in thread local storage. During execution, the thread also has access to a system timer which it can sample with microsecond or better precision with a single instruction. For any sequence of instructions within the thread for which execution time is to be measured, the sequence of instructions has an identifier and includes two commands, herein called a start command and an end command. The start command samples the system timer to obtain a start time, and stores the identifier and the start time in the timing buffer in the thread local storage. The end command samples the system timer to obtain an end time, and updates the data for the corresponding identifier in the timing buffer, to indicate an elapsed time for execution of the sequence of instructions. The start command and end command each can be implemented as a single executable instruction.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: Technologies are described herein for providing efficient in-place preservation of content in multiple, disparate content sources without disrupting end-users' access to the content or content sources. A preservation request comprising a specification of a content source and a filter specification is received and the content source is marked as “on hold.” If a content item in the content source is modified or deleted, a copy of the current version of the content item is placed in a preservation storage area. A trim job may be run periodically that removes content items from the preservation storage area that do not match the filter specification.

Abstract: 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.

Abstract: An electronic discovery (eDiscovery) application is used in managing an electronic discovery process across different electronic data sources using a central interface. The eDiscovery application assists in managing: authentication support for the different data sources; accessing the different data sources; placing holds on content across the different data sources; searching and filtering content across the different data sources; gathering data across the data sources; and the like. The eDiscovery application may be configured as an application on premise, a cloud based service and/or a combination of a cloud based service and an application.

Abstract: A method for monitoring search performance on a server computer includes determining the processing time for a plurality of operations related to a search on the server computer. The determined processing time for each of the plurality of operations is stored in a database. Aggregate processing times are determined for the plurality of operations and the aggregate processing times are stored in the database.

Abstract: 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.

Abstract: A filter object comprising a standard sending interface consumed from an object framework to send at least one filter value to at least one consumer object supported by the object framework and a user interface to allow a user to configure a connection between the filter object and a consumer object. A developer may create a consumer object with a receiving interface such that the consumer object may accept filter values in order to filter the data it may display to a user. However, a filter developer may create a filter object with a sending interface such that the filter object may send a filter value to consuming objects that implement a similar receiving interface. If the consumer object does not implement a receiving interface compatible with the filter object, the consumer object may not be able to receive filter values from the filter object.

Abstract: A computer implemented system comprising a server-side object framework implementing a standard communication interface, a filter object to send a filter value over the standard communication interface, and a consumer object to receive the filter value over the standard communication interface. A developer may create a consumer object with a receiving interface such that the consumer object may accept filter values in order to filter the data it may display to a user. However, a filter developer may create a filter object with a sending interface such that the filter object may send a filter value to consuming objects that implement a similar receiving interface. If the consumer object does not implement a receiving interface compatible with the filter object, the consumer object may not be able to receive filter values from the filter object.

Abstract: 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.