Microsoft Technology Licensing, LLC

Matthew James Ruhlen

Kirk A Glerum

Eric A LeVine

Michael Ronn Marcelais

Jeff David Mitchell

Rob M Mensching

Christopher J Brown

Charles Scott Walker

Brian T Hill

Sam Franklin Williams, Iii

Brian Kenneth Dewey

Mark Fields

William Kennedy

Kenneth John Yuhas, Jr

Tyler W Butler

Martin Abadi

Steven Miles Greenberg

Gareth Alan Howell

Marcus Eduardo Markiewicz

Michal Krzysztof Piaseczny

Sugandha SudeshKumar Kapoor

Zhenjun Zhu

Nicholas Michael Simons

Kiran Akella Venkata

Juraj Gottweis

Brendyn O'Dell-Alexander

Nicholas Allen Robarge

Alexei Vopilov

E Peter Oosterhof

Marc Christopher Ramsey

Yanlin Peng

Christopher Von Hansen

Boris Isaac Feldman

Manish Soni

Nisha Tekchand Singh

Bowen Xue

Brendyn O'dell-Alexander

Sugandha Sudeshkumar Kapoor

Kenneth John Yuhas Jr

Mark T Fields

Kenneth J Yuhas

Mark Timothy Fields

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

Techniques and technologies for protocols for accessing hosts are described. In at least some embodiments, a system includes a processing component, and a host protocol component. The host protocol component is configured to receive at a host a request from a client device, the request including a Uniform Resource Locator (URL) string locating a container or an ecosystem stored by the host; determine using at least a portion of the URL string whether the request is a container-related request or an ecosystem-related request; generate a response at the host including information responsive to the request, the information including the URL string locating the container or the ecosystem, and at least one response parameter corresponding to the request and associated with the container or the ecosystem; and transmit the response from the host to the client device.

Protocols for accessing hosts

Techniques and technologies for protocols for accessing hosts are described. In at least some embodiments, a system includes a processing component, and a host protocol component. The host protocol component is configured to receive at a host a request from a client device, the request including a Uniform Resource Locator (URL) string locating at least one of a container or an ecosystem stored by the host; determine using at least a portion of the URL string whether the request is at least one of a container-related request or an ecosystem-related request; generate a response at the host including information responsive to the request, the information including the URL string locating the at least one of the container or the ecosystem, and at least one response parameter; and transmit the response from the host to the client device.

An external service application discovery process that connects a host with an external application server running a service application allowing a user of a client computing device to work with a file via a web browser. The host brokers the functionality of an external application server and serves as the platform where interactions between the client computing device and the external application server occur. An open interface protocol, which is a shared communication protocol, allows the host to communicate instructions from the client computing device to the external application server. Through the external service application discovery process, the external application server describes functionality provided by the service application to the host. The host selectively makes the functionality provided by the service application available to users based on the level of implementation of the open platform interface and the conventions of the external service application discovery process understood by the host.

External service application discovery method

A host agnostic integration and interoperation system. The host agnostic integration and interoperation system includes an open platform interface and the associated conventions that define the roles of and direct operations between a host and a service application running on an external application server and allow the host to discover and integrate the functionality provided by the service application. The open platform interface employs a limited number of easily implemented semantic methods allowing a host to expose and integrate the ability to view, edit, or otherwise manipulate a document using the host supported functionality of the service application from a standard user agent. The host agnostic integration and interoperation system handles user authentication at the host using an access token and establishes a trust relationship between the host and the external application server using a lightweight but secure proof key system.

Host agnostic integration and interoperation system

According to some embodiments, a callback interface for web accessible services is provided. A Uniform Resource Locator (URL) or similar address is issued by a host associated service to the user. User's browser provides the URL to an activity service, which on the user's behalf contacts the host service indicated by the URL and supporting the callback interface. The activity service then facilitates the user's requests on documents maintained by the host service through stateless calls to the host service providing web accessible services such as document manipulation, image processing, and similar ones.

Interfacing distinct services for providing web based document manipulation access

Portions of content are transformed into portions of rendered content. While the portions of the content are being transformed into portions of the rendered content, each discrete portion of the rendered content can be provided to the application program after that portion is completed.

Content rendering on a computer

A system and method are disclosed for providing a resource, such as a document, to a client computing device. A request is received at a server from the client for particular named objects representing a portion of the document. It is determined that the particular named objects requested are contained in a particular chunk of a bundle. The bundle includes a plurality of named objects that comprise a version of the document that is rendered to be displayable by the client. It is determined that the particular chunk is not stored locally at the server, so the particular chunk is requested and received from bundle storage. The particular chunk, which includes the particular named objects requested and additional named objects, is stored locally by the server. The particular named objects are then sent to the client without sending the additional named objects to the client.

Efficient creation, storage, and provision of web-viewable documents

A procedure for preparing electronic resources for delivery to client computers is disclosed. When rendered on a browser for display, the electronic resources (e.g., web pages) include a reference link to another electronic resource. In response to receiving a request for delivery of a specific resource to a client computer, a server computer retrieves the resource from storage and examines the resource to locate any link identifiers contained therein. If a link identifier is detected, the network address corresponding to this link identifier is identified by the server and incorporated into the requested electronic resource in place of the link identifier. The prepared resource is then delivered to the client computer for rendering on a browser.

Abstracting links to electronic resources in a network environment

In a software development environment, a system and method for associating an assert with a unique identifier ('assert tag'), and using the unique identifier to store information associated with the assert in a database. Based on the unique identifier, information associated with the assert can be stored in a database or repository that contains assert information. This information can be updated, as well as displayed to the developer or tester. Information for the bugs associated with the assert can be retrieved from a database containing bug information and displayed to the developer or tester. Once the developer or tester has been presented with the information concerning the bugs associated with the assert, or other information associated with-the assert, the developer or tester can choose to enter or log-in a new bug into the database containing bug information.

System and method for storing and reporting information associated with asserts

Embodiments of the present invention relates to a method, system and computer-readable medium for redirecting a request URL. This redirection includes receiving the request URL from a user. The request URL includes data related to a patterned URL and data related to a destination URL. The patterned URL is determined based on the data related to the patterned URL from the request URL. A destination URL is generated based on one or more of the patterned URL, the data related to the destination URL from the request URL, and redirector configuration information.

Method and system for redirecting a request using redirection patterns

A computer-implemented method and system for reporting failures in an application program module to a corporate file server. The failure may be a crash or a set-up failure. Once detected, the program failures are categorized, i.e. bucketed, and reported directly to a local file server operated by a corporation. The corporate file server may be used to store the failures encountered by users in a corporate environment until these failures are reported to a server operated by the manufacturer of the program module (a destination server). Once the failures are reported to the destination server, developers or programmers may examine the data and determine what is causing the failures in the program module. A failure reporting executable on the user's computer provides communications between the failed application program module and the local file server. An administrative reporting executable (typically operated at the corporate file server) provides communications between the failure reporting executable and the corporate file server and between the corporate file server and the destination server. A cab tree, a counts tree and a status tree stores bucket information for a failure at the corporate file server. The bucket information for a crash may comprise an AppName, an AppVer, a ModuleName, a ModuleVer, and an offset into that module. The bucket information in the corporate file server may be uploaded to a destination server by a corporate system administrator thus preventing sensitive information from being disclosed by the corporation's users.

Method and system for reporting failures of a program module in a corporate environment

A method for categorizing information regarding a failure in an application program module. The failure may be a crash, a set-up failure or an assert. For a crash, a name of an executable module where the crash occurred in the application program module, a version number of the executable module, a name of a module containing an instruction causing the crash, a version number of the module and an offset into the module with the crashing instruction are determined. This bucket information is then transmitted to a repository for storage in a database. The database may be examined to determine fixes for the bug that caused the crash.

Method and system for categorizing failures of a program module

A system and method for handling the generation of an unexpected exception by an application. When the application generates an unexpected exception (i.e., crashes), the application's exception filter launches an outside exception handling program (EHP) that is separate and distinct from the application. Through a special protocol, the application and the EHP collaborate in responding to the unexpected exception. In this protocol, the application and the EHP communicate through kernel objects accessible by handles in a shared memory structure that the application creates before launching of the exception handling program and then shares with the EHP. Through this shared memory, the application also provides the EHP with information about the types of recovery options to offer the user. Through a graphical user interface, the EHP is then responsible for notifying the user of the application that an unexpected exception has occurred. Through the graphical user interface, the EHP also provides the user with the ability to specify various courses of action in response to the unexpected exception.

Method and system for handling an unexpected exception generated by an application

Growing community of inventors

Redmond, WA, United States of America

Matthew James Ruhlen