2.2.3.1.2.1 TransactionPropRetHeader
The server uses the TransactionPropRetHeader structure to communicate transaction status, and optionally to return additional data that advises the client to cancel the current transaction or to stop sending further information about it.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
m_usMaxVer |
m_usMinVer |
||||||||||||||||||||||||||||||
m_usFlags |
m_usVariant |
m_usMaxVer (2 bytes): The major version number for this TransactionPropRetHeader format; this field MUST be set to 0x0001.
m_usMinVer (2 bytes): The minor version number for this TransactionPropRetHeader format; this field MUST be set to 0x0001.
m_usFlags (2 bytes): This MUST contain 0x0000 or the bitwise OR of one or more of the following flags:
-
Value
Meaning
TransactionPropRetFlag_Abort
0x0001
The client MUST cancel the transaction.
TransactionPropRetFlag_DontSend
0x0002
The client SHOULD NOT send the currently active transaction (for example, either as a TransactionPropCallExportCookie (section 2.2.3.1.1.2) or as a TransactionPropCallTransmitterBuffer (section 2.2.3.1.1.3)) to the server again for the life of the transaction.
m_usVariant (2 bytes): This MUST be one of the following values:
-
Value
Meaning
TransactionPropRet_None
0x0000
The TransactionPropRetHeader structure MUST NOT be contained within any larger structures.
TransactionPropRet_Whereabouts
0x0001
The TransactionPropRetHeader structure MUST be contained as part of TransactionPropRetWhereabouts (section 2.2.3.1.2.2).