ITipHelper::PullAsync
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
This method provides applications with the option to asynchronously pull a transaction. By asynchronously pulling a transaction, the application can start work on the transaction before the pull completes. This mechanism provides for more parallelism. The application provides the TIP Transaction URL of the transaction to pull. The application also provides a pointer to a sink that will receive the pull completion status. The TM returns an ITransaction pointer to a transaction object. Similar to the ITipHelper::Pull method, the pszTxUrl parameter can refer to a transaction on the applications local TM or to a transaction on a remote TIP TM.
Note
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.
Syntax
HRESULT PullAsync( char ** pszTxUrlITipPullSink * pTipPullSinkITransaction ** ppITransaction
);
Parameters
pszTxUrl
[in] This parameter specifies the TIP Transaction URL of the transaction to pull.
pTipPullSink
[in] This parameter specifies the sink to call upon completion of the asynchronous pull operation.
ppITransaction
[out] This parameter returns an ITransaction pointer to the transaction object identified by pszTxUrl.
Return Values
S_OK
Success—the asynchronous pull request was queued.
E_OUTOFMEMORY
Failure—out of resources.
E_INVALIDARG
Failure—one or more of the parameters are not valid.
E_FAIL
Failure—generic failure while attempting to pull the transaction from the remote TM.
E_UNEXPECTED
Failure—an unexpected error occurred.
XACT_E_TMNOTAVAILABLE
Failure—unable to establish a connection with the DTC service.
XACT_E_CONNECTION_DOWN
Failure—the connection to the local transaction manager is down.
XACT_E_CONNECTION_DENIED
Failure—the transaction manager refused to accept a connection.
XACT_E_TIP_DISABLED
Failure—the Transaction Internet Protocol (TIP) service is disabled by default.
Requirements
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 txcoord.h