Microsoft Technology Licensing, LLC

Adrian Dragomir

Marc David McClure

Jianping Yin

Abolade Gbadegesin

Vishal Vikram Ghotge

Megan Galbraith Donahue

Yasser Elsayed Shaaban

Peter J Torr

Darin Miller

Jorge I Raastroem

Timothy Daniel Noonan

Rachel Jiang

Chittur Padmanabhan Subbaraman

Pavan Rajamohan Hullumane

Gregory Arthur De Souza

Juan Vicente Esteve Balducci

John Allen Atwood

Jeff West

Dennis A Kiilerich

Anish Desai

Robert Paul St Pierre

Gregory Bolles

Samuel Neely

Ashutosh Tewari

Kevin Grey

Kevin Daniel Resnick

Mark Sievert Larsen

Katy Chia-wen Chen

Lingeshwaran Palaniappan

Renata Van Diest

Marc Mcclure

Robert St Pierre

Marc David Mcclure

Peter John Torr

The subject disclosure is directed towards a background transfer service that provides platform-level support for third party applications to queue data transfers to run in the background, including when the application is not running in the foreground. Applications may thus perform downloading and uploading tasks in the background; however the background transfer service manages the data transfer requests so as to limit each background application's ability to interfere with foreground application operations, that is, by controlling resource usage according to one or more policies.

Background transfer service for applications on mobile devices

An application using one version of a schematized XML protocol communicates with another application using a different version of the schematized XML protocol. The different versions may correspond to different deployments or releases of the protocol. Each application generates messages to be sent using two data sets. A first data set is incorporated into the message using elements available in a standard XML protocol schema. A second data set is incorporated into the message using XML annotation elements. The receiving application processes the message using the schematized XML protocol to parse out the first data set. The receiving application further parses the message to identify the second data set that is carried by enhanced XML annotation elements. Extension or annotations are flexibly added to the XML protocol without requiring the client application to request&#x2014;or the server application to respond to&#x2014;a pre-negotiated number or type of annotations.

Extension of schematized XML protocols

The embodiments described herein generally relate to a method and system for synchronizing multiple classes with disparate schemas in a single collection through the use of the same synchronization request and/or synchronization key. A collection of different types of items may be synchronized while using the unique schema for each class. Further, different synchronization options, e.g., filtering, truncation, and body settings, may be applied to each class. In a synchronization request, an option block within a synchronization command notifies the server to synchronize the class specified in the option block. The option block may also specify the options, or settings, if any, to apply to the class. Multiple option blocks may be included in the synchronization command to specify the synchronization of multiple classes. Where multiple classes are specified, the server responds with the synchronized items of all such classes while maintaining each class's unique schema.

Synchronizing multiple classes with disparate schemas in the same collection

An invalid digital certificate can be saved and subsequently compared to an incoming digital certificate when performing a security check. If a subsequently provided digital certificate does not match the saved digital certificate, an error condition can be generated. Because a digital certificate can be invalid for non-malicious reasons, such technologies can be useful for improving software security.

Securely handling server certificate errors in synchronization communication

A synchronization system includes a first account assigned a first unique identifier. Access to the first account is contingent on validation of a shared access credential. The synchronization system also includes a second account assigned a second unique identifier. Access to the second account is contingent on validation of the shared access credential. The synchronization system further includes a library of account operations. One or more account operations are configured to utilize the first unique identifier when addressing the first account, and one or more account operations are configured to utilize the second unique identifier when addressing the second account.

Unique account identification

Growing community of inventors

Bellevue, WA, United States of America

Adrian Dragomir