DR. JAMES DAVID JOHNSON, DDS
Dentist at 116 Ave, Bellevue, WA

7730487, Jun 1, 2010

Aug 15, 2005

11/204209

William James Carley - Woodinville WA, US
James Ernest Johnson - Bellevue WA, US
John David Doty - Seattle WA, US
Jonathan Morell Cargille - Bellevue WA, US
Kapil Gupta - Redmond WA, US
Max A. Feingold - Bellevue WA, US
Michael R. Clark - Issaquah WA, US

Microsoft Corporation - Redmond WA

G06F 9/46

718101, 719313, 719320, 707 8

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.

7730095, Jun 1, 2010

Mar 1, 2006

11/365419

Tirunelveli Vishwanath - Redmond WA, US
Max A. Feingold - Bellevue WA, US
James E. Johnson - Bellevue WA, US

Microsoft Corporation - Redmond WA

G06F 7/00, G06F 17/30, G06F 15/16

707785, 707607

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.

8082344, Dec 20, 2011

Feb 12, 2007

11/673749

John D. Doty - Seattle WA, US
James E. Johnson - Bellevue WA, US
William James Carley - Woodinville WA, US
Kapil Gupta - Redmond WA, US

Microsoft Corporation - Redmond WA

G06F 15/173

709226, 709221

A transaction manager virtualization layer is provided for supporting multiple active transaction managers in a cluster or node. By virtualizing the transaction managers, applications and services are enabled to migrate across cluster nodes or even outside a cluster that includes relevant recovery mechanisms for transactions that are not completed at the time of migration. Multiple implementations of a transaction manager may be enabled to run side-by-side in a node or cluster allowing a rolling upgrade of transaction managers in clusters.

8166481, Apr 24, 2012

Jan 14, 2009

12/353905

Alexander Dadiomov - Redmond WA, US
Dana Groff - Sammamish WA, US
Yosseff Levanoni - Redmond WA, US
James E. Johnson - Bellevue WA, US

Microsoft Corporation - Redmond WA

G06F 9/46, G06F 7/00, G06F 12/00

718102, 718101, 718104, 707687, 707703, 711147, 711154

A transactional memory processing system provides for the integration of transactional memory concepts at the compiler-level into a higher-level traditional transaction processing system. Atomic blocks at the compiler-level can be specified as atomic block transactions and include the features of atomicity and isolation. Actions within this atomic block transaction include the enlistment of resource managers from a repository. The repository can now include a pre-programmed memory resource manager to manage the transactional memory. As in traditional transactions, a commit protocol can be used to determine if the actions are valid and can be exposed outside of the transaction. Unlike traditional transactions, however, the transaction is not necessarily doomed if all of the actions are not validated. Rather, memory conflicts can cause a rollback and re-execution of the atomic block transaction, which can be repeated as long as necessary, until the memory resource manger votes to commit.

7533080, May 12, 2009

Apr 10, 2006

11/401029

Dana D. Groff - Sammamish WA, US
James E. Johnson - Bellevue WA, US
John D. Doty - Seattle WA, US
Jonathan M. Cargille - Seattle WA, US
Kapil Gupta - Redmond WA, US
Michael R. Clark - Issaquah WA, US

Microsoft Corporation - Redmond WA

G06F 17/30

707 2, 718101

Minimizing transaction managers. A method that may be practiced in a commit tree topology including a plurality 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 acts for minimizing storage overhead by minimizing the number of transaction managers used to coordinate transactions. The method includes identifying a set of transaction managers. A first transaction manager is selected from among the set of transaction managers. A second transaction manager is identified from among the set of transaction managers that is always available when the first transaction manager is available. Messages are redirected from a subordinate associated with the first transaction manager to the second transaction manager.

8301706, Oct 30, 2012

Jun 15, 2009

12/484741

Kartik Paramasivam - Redmond WA, US
James E. Johnson - Bellevue WA, US
Nicholas Alexander Allen - Redmond WA, US
John Anthony Taylor - Bellevue WA, US
Margaret J. Lye - Redmond WA, US

Microsoft Corporation - Redmond WA

G06F 15/16

709206, 709217, 709225

Message intermediation for multiple service instances, while allowing the service instance to control whether messages are processed under a transaction. The message intermediator chooses to dispatch messages among different backend service instances based on any routing rules. The message intermediator performs a peek-lock of message from a forward-end queue, and assigns the message to a service instance. The message is provided into a backward-end queue specific to the assigned service instance. The service instance may then process the message, perhaps under a transaction created at the service instance. Upon completion of processing, the message is deleted in the back-end queue, which causes the forward-end queue to delete the message under the same transaction created by the service instance. Whether or not this deletion at the forward-end is committed or rolled back depends on whether the transaction created at the service instance is committed or rolled back.

7912973, Mar 22, 2011

Dec 3, 2004

11/004528

Max A. Feingold - Bellevue WA, US
David E. Langworthy - Kirkland WA, US
James E. Johnson - Bellevue WA, US
John D. Doty - Seattle WA, US
Michael R. Clark - Issaquah WA, US

Microsoft Corporation - Redmond WA

G06F 15/16

709230

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.

2009026, Oct 15, 2009

Apr 14, 2008

12/102837

Jeffrey P. Snover - Woodinville WA, US
Abhishek Agrawal - Seattle WA, US
Leigh C. Holmes - Renton WA, US
Cuneyt E. Havlioglu - Seattle WA, US
William James Carley - Woodinville WA, US
Vikram Sahijwani - Renton WA, US
Vitaly Bordovskiy - Kirkland WA, US
James Johnson - Bellevue WA, US
Kapil Gupta - Redmond WA, US

Microsoft Corporation - Redmond WA

G06F 9/46

718101

A computer system with a command shell that supports execution of commands within transactions. The command shell responds to commands that start, complete or undo transactions. To support transactions, the command shell may maintain and provide transaction state information. The command shell may interact with a transaction manager that interfaces with resource managers that process transacted instructions within transacted task modules to commit or roll back transacted instructions from those task modules based on transaction state information maintained by the shell. Parameters associated with commands can control behavior in association with transaction process, including supporting nesting transactions and non-nested transactions and bypassing transacted processing in some instances of a command.

7395264, Jul 1, 2008

Jul 23, 2004

10/898624

Joe D. Long - Woodinville WA, US
James E. Johnson - Bellevue WA, US
Michael R. Clark - Issaquah WA, US
Egidio Sburlino - Seattle WA, US
Gert E.R. Drapers - Amerongen, NL
Jagan M. Peri - Redmond WA, US
Dax H. Hawkins - Kirkland WA, US

Microsoft Corporation - Redmond WA

G06F 7/04

707 10

A transaction protocol is described that allows a database transaction to begin as a local, lightweight transaction without involving a distributed transaction coordinator and then be promoted to a distributed transaction only when required, e. g. when more than one database connection is required. A promotable enlistment allows a first resource to begin processing a promotable transaction. If the resource is notified that the transaction is being promoted to a distributed transaction, the resource is configured to promote the enlistment to a distributed transaction coordinator which coordinates processing of the transaction between the first resource and at least a second resource.