Microsoft Technology Licensing, LLC

Satish Ramchandra Thatte

Johannes Klein

Gopal Krishna R Kakivaya

Bimal Kumar Mehta

Andrew Layman

Rolando Jimenez Salgado

Todd J Abel

Rahul Kapoor

Richard Douglas Hill

Anthony Dean Andrews

Rebecca Ann Norlander

Sanjib Saha

James M Lyon

Paul Maybee

Lee B Graber

Anuj Bansal

Ricard Roma I Dalfo

Alex Burst

Luis Felipe Cabrera

Dharma Kiritkumar Shukla

Jan Stephen Gray

Robert George Atkinson

Paul F Ringseth

Henrik Frystyk Nielsen

Craig Henry Wittenberg

Abhay Vinayak Parasnis

David G Green

Lucius Gregory Meredith

Marc Levy

Maarten Mullender

Eric Wendell Johnson

Greg Prickril

Anton Kirillov

Alexander A Armanasu

LiHui V Xu

Mark C McLoughlin

Sriram Balasubramanian

Scott G Robinson

Christian F Huitema

Christopher G Kaler

Wei Xiao

Erik B Christensen

John Peter Shewchuk

Christopher Wellington Brumme

Michael Joseph Toutonghi

David E Langworthy

Kartik Paramasivam

Vladimir Pogrebinsky

Girish Mittur Venkataramanappa

Alfred Lee

Eldar Azerovich Musayev

Jean-Emile Elien

Kevin Bowen Smith

Eddie Fusaro

Anandhi Somasekaran

Xiaoyu Wu

Ricard Roma I Dalfó

Arunachallam Sivaprakasam Sivakumar

Yi Mao

Kaushik Raj

Saji Varkey

Richard Roma iDalfo

Ricard Roma Dalfo

Mark H Lukovsky

Neilton J Saari

Henrik F Neilsen

Flavio Paiva Junqueira

The present invention extends to methods, systems, and computer program products for increasing coordination service reliability. A coordination service maintains state (e.g., using replication) for one or more software components (e.g., applications). Tokens can be used to identify incarnations of a member set within the coordination service. When a member starts and has no token, the member attempts to learn the token from a majority other members. If no such token exists, the member requests a new token. Aspects of the invention can be used to detect and compensate for lost state within the coordination service, including state lost due to storage device failures (which may be referred to as 'silent data loss'). Detecting and compensating for silent data loss makes the coordination service more reliable and can essentially guarantee that the coordination service notifies clients when data is lost and ceases processing when incorrect state may exist.

Increasing coordination service reliability

Techniques to manage event notifications are described. An apparatus may comprise a server having an event notification component. The event notification component may have an event agent component to receive a message indicating a change event for line of business (LOB) data, and convert the change event to a defined LOB entity event. The event notification component may have a notification service component to generate a LOB event message for the entity event. The event notification component may have an event database to store the event message in a user event queue. Other embodiments are described and claimed.

Techniques to manage event notifications

Techniques to cross-synchronize data are described. An apparatus may comprise a cross-synchronization component to synchronize multiple data items for different application programs between multiple client devices synchronized using multiple synchronization circuits. The cross-synchronization component may determine whether changes to the multiple data items made at a first client device are propagated to a second client device using consistency information maintained by a consistency group item for a consistency group including the data items. Other embodiments are described and claimed.

Techniques to cross-synchronize data

Techniques for enterprise data as office content are described. An apparatus may comprise a client device having an application program, an insertion component and an update component. The insertion component may be arranged to insert source data elements from a data source into a document for the application program. The update component may be arranged to update the inserted data elements as the source data elements are modified. Other embodiments are described and claimed.

Enterprise data as office content

An XLANG/s compiler detects convoy scenarios during compilation and generates runtime directives to correctly correlate incoming messages with business process instances. A convoy scenario, present in event driven processes, is defined by a correlation set initialized during a receive operation which is provided to a subsequent receive operation. The compiler detects those convoy scenarios by analyzing the control and dataflow of a XLANG/s program. Three convoy patterns are distinguished: (1) activation convoys, (2) uniform sequential convoys, and (3) non-uniform sequential convoys. XLANG/s allows declarative descriptions of convoy scenarios without requiring an understanding of the low-level details supporting their correct execution. Convoy scenarios are processed by statically analyzing a written workflow application to deduce the nature and type of convoy scenarios used by the application. Information is extracted at compile time to support the runtime infrastructure. The runtime infrastructure is tightly integrated with the underlying correlation and subscription evaluation framework.

Efficient processing of a convoy workflow scenario in a message driven process

Designing and executing a workflow having flow-based and constraint-based regions. A user selects one or more activities to be part of a constraint-based region. Each constraint-based region has a constraint associated therewith. The workflow is executed by executing the flow-based region and the constraint-based region. The flow-based region executes sequentially. The constraint is evaluated, and the constraint-based region executes responsive to the evaluated constraint.

Unified model for authoring and executing flow-based and constraint-based workflows

Techniques for host context framework are described. An apparatus may comprise a client device having a host application program with multiple host item objects, and a host context manager to manage multiple host contexts corresponding to the host item objects. The host context manager may create a host context for each host item object, and perform operations for each host item object in accordance with the corresponding host context. Other embodiments are described and claimed.

Host context framework

A routing protocol is provided for exchanging messages between an initial sender and an ultimate receiver, potentially via a set of intermediaries. The routing protocol provides an optional reverse message path that enables two-way message exchange patterns. The routing protocol can be expressed as a header entry within a message envelope, is independent of the underlying protocol, and can be generated at the application layer of a protocol stack. The routing protocol may allow each intermediary to process the message and dynamically alter the message path en route to the intended recipient.

Routing of network messages

A single virtual image of client information centrally located at an always-on network location for maintaining equivalency among multiple user devices. The image can be accessed by the user devices when coming online to upload and receive changes in the client information. A mid-tier system can be employed as the always-on central location with which the user client machines can communicate to maintain the same set of client information. Services in support thereof include an ownership service for dynamic selection of a designated client machine to take ownership for performing the actions on one client machine and arbitration of duplicate requests, a notification service for allowing data sources to publish cache update instructions to a central place, a roaming service for allowing clients machines to share state with each other, and an encryption service for secure storage and communications of client information.

Single virtual client for multiple client access and equivalency

Versioning and concurrency control architecture of data operations on data of a data source by multiple independent clients of a user. Data operation messages between the clients and the data source are intercepted and tracked for serialization control to a data view instance of the data source. The architecture can be located as an always-on centrally-located system (e.g., mid-tier), accommodate data operations that include create, read, update, delete, and query (CRUDQ) against data sources, and provides support for distributed transactions, locking, versioning, and reliable messaging, for example, for data sources that do not expose such capabilities. A hash is employed for version control and to control changes at the data source. The central system also provides logic for the individual CRUDQ operations, and granular error classification to enable retries whenever possible.

Versioning and concurrency control for multiple client access of data

Signals are mapped from one protocol to another protocol. A first protocol is received, and a mapping interface is generated to a second protocol. The first protocol is then mapped to the second protocol in accordance with the mapping interface. The mapping interface may comprise a coordination map. Moreover, a state diagram may be generated that is based on the first protocol, prior to mapping the first protocol to the second protocol. The first protocol may be an abstract protocol or a web services business activity protocol, for example, and the second protocol may be another abstract protocol, a concrete interface, a web services interface, a common language runtime interface, or a business process execution language for web services, for example.

Generalized protocol mapping

Growing community of inventors

Redmond, WA, United States of America

Satish Ramchandra Thatte