TIP Usage Scenarios
The following topics in this section describe two usage scenarios for the DTC TIP extension interfaces:
Each scenario outlines the order of method calls and the message flows made to propagate transaction context using the interfaces.
The scenarios assume that all transaction managers implement the Transaction Internet Protocol correctly and send the "IDENTIFY" command before beginning a conversation with their partners. If the client decides to commit the transaction, the clients transaction manager sends a TIP "COMMIT" command to its partner and starts the two-phase commit. If the client decides to abort the transaction, the clients transaction manager sends a TIP "ABORT" command to its partner to abort the transaction. In either case, the transaction managers must do the regular processing to commit or abort the resources enlisted on the transaction.
|The TIP service feature is deprecated. The TIP service feature and all related APIs are available for use in the operating systems listed in the Requirements sections of the reference topics for those APIs. They might be unavailable in subsequent versions of the operating system. You might consider using the WS-AtomicTransaction (WS-AT) protocol as a replacement transaction coordination and propagation technology. WS-AT support is provided through Windows Communication Foundation (WCF) as part of the .Net Framework. For more information about WS-AT support in the .Net Framework see Transactions.|