Microsoft Technology Licensing, LLC

Max A Feingold

James Ernest Johnson

John David Doty

Michael Ray Clark

Kapil Gupta

Christopher G Kaler

Tirunelveli R Vishwanath

David E Langworthy

Jonathan M Cargille

Michael Marucheck

Harris Syed

Andrew D Milligan

Saji Abraham

Jim Johnson

Erik B Christensen

Kenneth David Wolf

Richard L Hasha

Donald F Box

Stephen James Millet

David Wortendyke

Giovanni Moises Della-Libera

Bradford H Lovering

Lance Olson

Richard Douglas Hill

Stefan R Batres

Umesh Madan

Michael James Coulson

Stefan Harrington Pharies

Craig Andrew Critchley

Vijay Gajjala

Uday Sooryakant Hegde

Elliot Lee Waingold

Krishnan Srinivasan

Matthew Thomas Tavis

Tomasz Janczuk

Geary L Eppley

Stephen T Swartz

David Edwin Levin

William J Carley

Michael Steven Vernal

Shy Cohen

Richard Dievendorff

Natasha Harish Jethanandani

Douglas M Purdy

David Owen Driver

Saurab Nog

Aaron Stern

Siddhartha Puri

Douglas A Walter

Jesus Ruiz-Scougall

Anastasios Kasiolas

Ryan Thomas Sturgell

Vipul A Modi

Alexander Martin DeJarnatt

Sowmyanarayanan K Srinivasan

Scott Christopher Seely

Jonathan T Wheeler

Mohammad Makarechian

Evgeny Osovetsky

Chaitanya Dutt Upadhyay

Michael Thomas Dice

Yaniv Pessach

Mauro Ottaviani

Erin Honeycutt

Eugene Shvets

Alfred M Lee, Iv

Yasser Shohoud

Michael Abbott

Anand Rjagopalan

Mohamed-Hany Essam Ramadan

Serge Sverdlov

Vaithialingam B Balayogan

Including support for advanced protocols in propagation information transferred between applications. Transaction managers associated with the applications communicate with each other to complete a transaction. Rather than communicating using a standard protocol, embodiments of the invention enable a first transaction manager to identify advanced protocols supported by the first transaction manager to a second transaction manager using existing propagation tokens. The second transaction manager selects one of the supported protocols to communicate with the first transaction manager to complete the transaction.

Dynamic transaction protocol upgrades

The present invention extends to methods, systems, and computer program products for fitness based routing. Embodiments of the invention significantly improve the likelihood that routing nodes contained in routing table have adequate (or even relatively increased) ability to transfer and process messages in an overlay network. Thus, when the node is to make a routing decision for a message, the node has some assurances that any selected routing node is adequate (or is at least the best currently available). Further, a sending node can take preference to routing nodes with higher fitness values when sending a message. Preference to higher fitness metric values further insures that messages are adequately transferred and processed. Accordingly, embodiments of the invention can be used to route messages in a manner that optimizes bandwidth and provides efficient routing capability.

Fitness based routing

A mechanism for negotiating a relatively transport agnostic communication protocol for use in accomplishing a distributed activity. The potential protocols subject to negotiation may be, for example, extensions to Web Services Coordination. In that case, when the initiator creates a transaction, the initiator also negotiates the desired protocol with its transaction manager. The transaction manager and any other participants in the transaction will then follow that negotiated protocol when communicating with the transaction manager. The protocol may be selected to improve performance and may be tailored to existing needs and capabilities.

Message exchange protocol extension negotiation

Mechanisms for securely allowing a participant computing entity to engage in a transaction initiated by an initiator computing entity and managed by a coordinator computing entity. The initiator provides a transaction initiation request to the coordinator. Upon receipt, the coordinator accessing a transaction coordination context that includes information such as a secure key that may be used by a participant to register in the transaction. The coordinator then provides the coordination context to the initiator, which provides the coordination context to the participant(s) that are also to engage in the transaction. Each participant then generates a registration request that is based on the coordination context, and that is secured using the secure key provided in the coordination context.

Mechanism for secure participation in a transaction by a third party

The present invention extends to methods, systems, and computer program products for controlling transactions in accordance with role based security. A first transaction related component receives a transaction related message from a second transaction related component. The transaction related message indicates a request by the second transaction related component to perform a transaction related operation that is to involve the first transaction related component. The first transaction related component authenticates the second transaction related component. The first transaction related component refers to transaction control information indicating roles the second transaction component is permitted to assume relative to the first transaction related component. The transaction related operation indicated in the request is compared to the permitted roles for the second transaction related component. The transaction related operation is implemented in accordance with the results of the comparison.

Controlling transactions in accordance with role based security

The present invention extends to methods, systems, and computer program products for synchronizing ambient state among multiple transaction managers. A coordinating transaction manager establishes transaction ambient state for an application initiated transaction. The coordinating transaction manager sends and a subordinate transaction manager receives a pointer to an ambient state delegate. The subordinate transaction manager sends a request to invoke the ambient state delegate to the coordinating transaction manager in response to receiving an operation. The coordinating transaction manager invokes the ambient state delegate to format the transaction ambient state for the subordinate transaction manager. The coordinating transaction manager sends and the subordinate transaction manager receives the formatted transaction ambient state such that the subordinate transaction manager can appropriately process the operation within the scope of the transaction. The subordinate transaction manager utilizes the formatted transaction ambient state to appropriately process the operation within the scope of the transaction.

Synchronizing transaction ambient state among multiple transaction managers

Discovering transaction managers participating in a transaction. A method may be practiced, for example, in a commit tree topology including a number of transaction managers to manage transactions. The transactions include a set of operations that are all performed if a transaction is completed or all aborted if a transaction is not completed. The transaction managers store transaction result information to allow recovery of a transaction in case of system failure. The method includes receiving at a first transaction manager, a token from a second transaction manager on a machine external to the first transaction manager. The token specifies that the first transaction manager is the originator of the token. The token is associated with a transaction. The first transaction manager identifies that it has not previously participated in the transaction associated with the token. A transaction manager is identified that is participating in the transaction associated with the token.

Discovering transactions silently propagated off-machine

Example embodiments of the present invention provide a mechanism for allowing developers to define new interfaces and insert custom translational code that implements these new interfaces for legacy components that otherwise cannot communicate in a web service environment. These new interfaces are then exposed to the web service client in such a way that abstracts the web service client from the legacy components interfaces. The objects that implement the new interfaces are referred to herein as 'service surrogates' and the new interfaces will be commonly referred to as a, 'surrogate interfaces.' These surrogate interfaces may be initialized along with an instance of the service surrogate upon startup of an application that offers the services. In addition, a dynamic web service can simultaneously run along with the service surrogate for those services that may not need the features offered by the service surrogates.

Generating a dynamic web service and dynamic service surrogate for legacy application components

The present invention provides a mechanism that allows an administrative event to trigger or cause the generation of a dynamic web service during initialization of legacy application components. Similar to other types of static tooling approaches, the dynamic approach&#x2014;as supported herein&#x2014;uses available metadata describing an interface for communicating with legacy components. Rather than generating and manifesting the web service via tooling on a one time or occasional bases, however, example embodiments provide for the generation of the web service by the supporting infrastructure as a standard part of application initialization. Upon stopping the application, a termination sequence is provided that stops the corresponding dynamic web service and deletes the web service description used to generate the dynamic web service. Accordingly, every time the application is started the available metadata will need to be consulted and a consistent service will be built on-the-fly.

Dynamic service generation for legacy components

A web services namespace pertains to an infrastructure for enabling creation of a wide variety of applications. The infrastructure provides a foundation for building message-based applications of various scale and complexity. The infrastructure or framework provides APIs for basic messaging, secure messaging, reliable messaging and transacted messaging. In some embodiments, the associated APIs are factored into a hierarchy of namespaces in a manner that balances utility, usability, extensibility and versionability.

Interface infrastructure for creating and interacting with web services

Growing community of inventors

Bellvue, WA, United States of America

Max A Feingold