Microsoft Technology Licensing, LLC

Steven E Lees

Jack E Ozzie

Paresh S Suthar

Ransom Lloyd Richardson

Jason Evan Schleifer

John R Burkhardt

Marcus J Andrews

Richard Zack Speyer

Kiran Muthabatulla

Lukasz Konrad Brodzinski

Ilan Gabriel Caron

Alan W Carter

David Gordon Bradlee

Katherine Blair Huffman

Mark L Roberts

Jocelyn Berrendonner

Dennis Mark Canady

Katie Anderson

Hideyuki Nagase

Marcus John Andrews

A synchronization adapter is coupled to the application that does not support synchronization and generates the necessary synchronization metadata for all data in the application that is to be synchronized. The synchronization adapter then combines the metadata to the actual data to be synchronized to form a synchronization feed. The synchronization feed is stored in an internal cache (or data store) which is internal to the application, or an external cache (or data store), which is external to the application, or it can be stored in both caches. The synchronization adapter also intermittently determines whether the application data has changed, thus warranting a change in its metadata, or whether a synchronization operation is warranted to synchronization operation is warranted to synchronize the data with data in another application. In either case, the synchronization adapter makes the changes to the data, or performs a synchronization operation.

Synchronization adapter for synchronizing application data

Methods and devices for presenting an image in an atomic manner across a plurality of displays of a computer device from a single buffer shared by the plurality of displays may include synchronizing the plurality of displays of the computer device. The methods and devices may initiate an atomic present request to present an image frame on the plurality of displays including a first display and a second display, the atomic present request may identify at least a first display texture and a second display texture from a plurality of display textures stored in the single buffer corresponding to the image frame and that the first display texture corresponds to a first display and the second display texture corresponds to a second display. The devices and methods may transmit a bundled set of first image frame data and second image frame data from the single buffer to a display driver.

Mechanism to present in an atomic manner a single buffer that covers multiple displays

Described are examples for adjusting display level properties across multiple displays. One or more ranges of display brightness capability values that are supported by a given display device can be received for multiple display devices. For each of the multiple display devices, at least a portion of display brightness capability values in the one or more ranges of display brightness capability values can be mapped to selectable brightness levels available in an operating system. One of the selectable brightness levels can be determined as selected via the operating system. For each of the multiple display devices, a corresponding display brightness capability value mapped to the one of the selectable brightness levels can be determined and indicated to each of the multiple display devices, such that the multiple display devices may set different display brightness capability value brightness, but the brightness may be perceptually similar across the display devices.

Techniques for supporting brightness adjustment across multiple displays

Methods, systems, and computer-readable media are provided to allow multiple server resources to share a single connection to a client device. The single connection may be maintained between a notification queue on the server side and the client device. Multiple server resources share the notification queue. When a resource changes or a service wants to communicate information to a client, corresponding messages are sent to the notification queue over a connection within the data center. Once in the notification queue, the updates are communicated to the client device.

Subscribing to multiple resources through a common connection

Synchronization adapter for synchronizing data to applications that do not directly support synchronization

Methods, system, and computer storage media are provided for moderating actions performed on shared data objects. Rule enforcement logic is received for an application that is associated with one or more data objects shared between various clients. The rule enforcement logic is stored at a data server that also stores data associated with data objects. A moderator, also stored on the data server, is used to enforce the rule enforcement logic corresponding to the application when a client attempts to perform an action to a data object associated with the application.

Moderation of shared data objects

Methods, systems, and computer-readable media for manipulating in-memory data entities are provided. Embodiments of the present invention use a Representational State Transfer ('REST') web service to manipulate the in-memory data entities. In one embodiment, a 'snap shot' is taken of the in-memory data entities at a point in time to create representations of the entities. A hierarchy of the representations is built. The hierarchy is used to make the entities addressable via a URI. Embodiments of the invention may then map the entity representations in the hierarchy to the entities. An embodiment of the invention uses handlers to process a REST style request addressed to an entity representation. The handler reads the command and determines whether the command is authorized for performance on the entity and performs that command, if appropriate.

Providing access to shared state data

Methods, system, and computer storage media are provided for enabling cross-language object sharing by providing shareable typename information agreed upon by clients that wish to share object with each other. A first client creates an object by communicating a create request, which includes typename information associated with the object. The object is created and the typename information, along with data and properties associated with the object, is stored. A second client requests to open that object. The data, properties, and typename information stored in associated with the object is communicated to the second client so that the second client is able to create a correct instance of the object.

Cross language object sharing

Source code including application defined expressions and non-conforming identifiers are compiled to executable code. The source code is written with an application defined expression or non-conforming identifier enclosed between a predefined pair of matching separators, such as square brackets. When a sequence of characters between the predefined separators is encountered in the source code during compiling, a symbol table is searched for a matching identifier. If found, the characters are interpreted as a non-conforming identifier and bound to the matching identifier. If not found, the characters are interpreted as an application defined expression and bound to a function call for an evaluating function provided in an application library.

Growing community of inventors

Seattle, WA, United States of America

Steven E Lees