Microsoft Technology Licensing, LLC

John Heinrich Lueders

Jane T Kim

Bryan T Starbuck

Gail Giacobbe

Warren G Stevens

Alexander Vaschillo

Stephen Thomas Wells

Robert C Combs

Sridhar Sundararaman

Raghavendra Rachamadugu

Hubert Louis Marie Van Hoof

Sean O Lyndersay

Bruce Alan Morgan

Raju Jain

Amar S Gandhi

Robert Paul St Pierre

William Gould

Wayne Wy Choi

Michael John Novak

Aaron Naoyoshi Sheung Yan Woo

Anshul Rawat

Elizabeth Picchietti Salowitz

Mohammed Samji

Jon Robert Berry

David B Perry

David Ruzyski

Randy Knight Winjum

Shawn M Woods

Andrew S Zeigler

Daniel James Plaster

Calvin Tonini

Mary-Lynne Williams

Jess Holbrook

Sarah J Bowers

Prashant Singh

Louis A Martinez

Kuei-Chih Sun

Jennifer C Trahan

Avrum S Laurie

Wayne W Y Choi

Stephen T Wells

Alexander E Vaschillo

Gail Borod Giacobbe

Files can be located using a durable and universal file identifier. A content URI includes a file protocol URI specifying a path to a file. The file protocol URI includes a query string specifying properties of the file that can be utilized to locate the file, such as an object ID property specifying a GUID for the file and a volume ID property specifying a GUID for a storage volume storing the file. The content URI can be utilized to locate the file using the file protocol URI and its associated query string even if the file has been moved, renamed, or is accessed on a different computing device. Operations can then be performed using the file, such as resuming a previously performed activity that used the file.

Locating files using a durable and universal file identifier

A contextual file manager is described herein. Contextual information regarding files and folders of a file system of an operating system is collected. The contextual information may be collected from a variety of different sources, such as contents of the file or folder, an application associated with the file, a service provider, or a cloud storage service. The contextual information is then exposed in a file system interface of the operating system along with representations of the files and folders. In some cases, the contextual information is exposed in response to detection of an intuitive user action to a representation of one of the files or folders via the file system interface.

Contextual file manager

A cloud content states framework is described herein. In implementations, a framework is configured to perform operations for management of cloud content files at the computing device on behalf of cloud storage providers. The framework is operable to manage states for cloud content files accessible from multiple cloud storage services. The framework also manages and outputs state indicators with file system representations of the cloud content files. The states include at least a set of primary states indicative of synchronization status controlled by the framework. The states may also include custom states associated with cloud storage services that are defined via an interface exposed by the framework. In operation, states associated with cloud content files are recognized in connection with rendering a user interface with cloud content file representations. Then, state indicators that reflect the recognized states are exposed along with cloud content file representations in the user interface.

Cloud content states framework

A content syndication platform, such as a web content syndication platform, manages, organizes and makes available for consumption content that is acquired from the Internet. In at least some embodiments, the platform can acquire and organize web content, and make such content available for consumption by many different types of applications. These applications may or may not necessarily understand the particular syndication format. An application program interface (API) exposes an object model which allows applications and users to easily accomplish many different tasks such as creating, reading, updating, deleting feeds and the like. Further, in at least some embodiments, a user can subscribe to a particular web feed, be provided with a user interface that contains distinct indicia to identify new feeds, and can efficiently consume or read RSS feeds using both an RSS reader and a web browser.

Finding and consuming web subscriptions in a web browser

Various embodiments utilize certain events that occur within a Web browser to recognize an imminent intent, on the part of the user, to navigate to a website. Given such events, in combination with a user's past browsing patterns and history, an automated and personalized navigation solution can be provided to expedite navigation.

Determination and display of relevant websites

Various embodiments provide a guard mechanism that is configured to prevent transmission of synchronous function calls to hung application components. In at least some embodiments, a hang resistance application layer intercepts a synchronous function call that is intended for an application component. Before permitting the synchronous function call to be transmitted to the application component, the hang resistance application layer determines whether the application component is hung by transmitting a message other than the synchronous function call to the application component that requests that a response be received before transmission of the synchronous function call to the application component is permitted. Responsive to determining that the component is hung, a hung component recovery process is initiated.

Hang recovery in software applications

Various embodiments provide a guard mechanism that is configured to prevent transmission of synchronous function calls to hung application components. In at least some embodiments, the guard mechanism receives a synchronous function call that is intended for an application component. Before permitting the synchronous function call to be transmitted to the application component, the guard mechanism determines whether the component is hung. Responsive to determining that the component is not hung, the guard mechanism permits the synchronous function call to be transmitted to the component. If, however, the guard mechanism determines that the application component is hung, a hung component recovery process is initiated.

The principles of the present invention extend to efficiently and reliably providing message related data. Generally, data fields of electronic messages and attachments are created in accordance with an electronic message schema hierarchy. An electronic message can include links to folder items that represent message folders. An electronic message can also include links to contact items that represent message participants. Message applications can register for folder spaces such that each message application is aware of folders that are primarily controlled by other message applications. A link to a contact item can be selected to access current contact related data for a message participant, even when the contact related data has changed since an electronic message containing the link was received.

Efficiently and reliably providing message related data

The present invention extends to methods, systems, computer program products, and data structures for efficiently storing and accessing electronic messages. Generally, electronic messages are created and transformed in accordance with an electronic message schema hierarchy. Electronic messages can be created according to a general message schema that defines a format for data fields that are common to all types of electronic messages (e.g. electronic mail, instant message, fax message). Electronic messages can also be extended according to message extension schemas that define formats for adding protocol specific and/or or application specific data fields to an electronic message. Data fields added in accordance with message extension schemas can differ between electronic messages types. Having some commonly defined fields and other differently defined fields promotes efficient storage and access of electronic messages, while also facilitating message compatibility with existing message protocols and message applications.

Schema hierarchy for electronic messages

The present invention extends to methods, systems, computer program products, and data structures for decoupling an attachment from an electronic message that included the attachment. Generally, data fields of electronic messages and attachments are created in accordance with an electronic message schema hierarchy. Attachments are configured to have a data field indicating if the attachment is to persist when a corresponding electronic message is deleted. When an attachment persists, a user may be able to locate and use the attachment after a corresponding electronic message has been deleted (even if the attachment has not been expressly saved). Attachments are configured to include attachment metadata indicating properties of an electronic message that included the attachment. Accordingly, a user can access information (e.g., sender, subject, date, etc) associated with an electronic message (e.g., that included the attachment) even after the electronic message has been deleted.

Decoupling an attachment from an electronic message that included the attachment

Growing community of inventors

Seattle, WA, United States of America

John Heinrich Lueders