Microsoft Technology Licensing, LLC

Shawn M Woods

Daniel James Plaster

Jon Robert Berry

John Heinrich Lueders

David Ruzyski

Andrew S Zeigler

Mehmet Iyigun

Yevgeniy Bak

Michael J Patten

Blair Brewster Dillaway

Mark Yalovsky

Rolf Arnold Ebeling

John L Manferdelli

Michael J Ens

Stuart Sechrest

Jeffrey Che Fuller

Phu Hoang Le

Yau Ning Chin

Peter Seraphim Ponomarev

Prashant Ratanchandani

Ryan M Hurst

Christina L Rhodes

Jason Carl Hendrickson

Ishfaq Mohammad Ismail

Herman H Ng

Ashmi S Bhanushali

John Corey Morgan

Jonathan M Au

Hemchand Alla

Alex J Glover

A Web application maintains a record of Web content that has been displayed by the Web application. The user can navigate to different previously displayed Web content by providing various user inputs, such as a swipe across a touchscreen. The Web application detects when a user input has a threshold likelihood of being a navigation input, such as when the user swipes at least a threshold amount across a touchscreen. When a user input has a threshold likelihood of being a navigation input, the Web application begins rendering in an empty tab the Web content that would be navigated to if the user input were a navigation input, the empty tab becoming a prerender tab. If the user continues and the user input results in a navigation input navigating to the Web content rendered in the prerender tab, then the Web application switches to displaying the prerender tab.

Web content navigation using tab switching

Two different process management views can be displayed, and a user can request to switch between the two views. The user can select a process in either view and have the selected process terminated. One view is a simplified view that identifies processes and whether they are non-responsive. The other view is an expanded view that identifies processes and the amount of various system resources used by each of those processes. Various additional information can be displayed in the expanded view, such as identifiers of various windows, tabs, and/or services associated with each of the processes.

Process management views

Various embodiments provide message queue management techniques designed to reduce the likelihood of multi-component applications becoming nonresponsive and enable recovery options for individual components if they do become nonresponsive. In at least some embodiments, a message queue manager detects when a component of an application interface becomes nonresponsive and detaches the component from a shared message queue. The shared message queue can continue to process messages for other responsive components while messaging for the nonresponsive component is managed via a separate queue. The message queue manager can also notify a user regarding the nonresponsive component and provide the user with options to facilitate recovery of the nonresponsive component. Further, in at least some embodiments, the message queue manager can monitor a detached component and reattach the detached component when it becomes responsive again.

Message queue management

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.

An access control policy engine associated with a resource determines whether to allow a request to access same. The engine receives the request with an security token, retrieves the token determines a type thereof, and maps access decision information in the token to a common format as at least one security claim setting forth adequate information to determine a right of the requestor. Thereafter, the engine retrieves a set of rules for accessing the resource, applies the rules to the security claims to determine whether to allow the request from the requestor, and if the request is to be allowed, provides the requestor access to the resource in accordance with the request and the rights of the requestor as determined based on the security claims.

Access control policy engine controlling access to resource based on any of multiple received types of security tokens

Growing community of inventors

Seattle, WA, United States of America

Shawn M Woods