Updated: July 19, 2016
Applies To: Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server Technical Preview, Windows Vista
The DTC Proxy calls the methods of this interface to deliver phase zero notification to a Phase0 participant, and to notify the participant that the asynchronous enlistment has completed.
An application wanting to receive phase 0 notification on a transaction implements this interface. Typically various cache managers would require phase 0 notification to trigger a flush on a cache that has been updated in a transaction.
Use this interface to receive phase zero notification from the DTC Proxy.
- IUnknown methods
|Phase0Request||Notifies a Phase0 participant that the transaction manager has issued the phase 0 notifications.|
|EnlistCompleted||Notifies a Phase0 participant that the process of enlisting with the TM is complete.|
You supply a pointer to this interface when calling the ITransactionPhase0Factory::Create method.
When processing a callback, there are a few restrictions on what can be performed. Since the callback is running on a DTC CM thread, which is a scarce resource, the callback should not make any blocking DTC calls, nor should it block on any user-level locks unless they are guaranteed to be available very shortly in spite of blocking. Failure to abide by these restrictions can result in deadlock situations.
For an explanation of the requirement values, see Requirements (Component Services).
Platforms: Windows Server 2016, Windows 10, Windows Server 2012 R2, Windows 8.1, Windows Server 2012, Windows 8, Windows Server 2008 R2, Windows 7, Windows Server 2008, Windows Vista
Header: Declared in txdtc.h