2.2.2.2.1 ProtocolInformationFlags
The ProtocolInformationFlags is a byte field specifying network and security settings of the transaction coordinator endpoint.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
bitFieldEncoding |
|||||||||||||||||||||||||||||||
bitFieldEncoding (1 byte): The bits of this field MUST be encoded as follows.
-
0
1
2
3
4
5
6
7
8
91
0
1
2
3
4
5
6
7
8
92
0
1
2
3
4
5
6
7
8
93
0
1T
N
I
O
C
A
B
C
-
T (1 bit): A flag indicating whether the transaction coordinator supports the use of security context tokens, as specified in [WSSC] and [WSAT11]. If the value is 1, then security context tokens are supported; otherwise, they are not.
-
N (1 bit): A flag indicating whether the Activation Service SPNEGO endpoints are available, as specified in sections 2.2.2.3.3 and 2.2.2.3.4. If the value is 1, then endpoints are enabled; otherwise, they are not.
-
I (1 bit): A flag indicating whether or not the transaction coordinator supports registration requests for Two-Phase Commit Protocol. If the value is 1, then registration requests for Two-Phase Commit Protocol are supported; otherwise, they are not. If the value of this flag is not 1, then the value of the "O" flag MUST be 1.
-
O (1 bit): A flag indicating whether or not the transaction coordinator supports requesting registration for Two-Phase Commit Protocol. If the value is 1, then requesting registration for Two-Phase Commit Protocol is supported; otherwise, it is not. If the value of this flag is not 1, then the value of the "I" flag MUST be 1.
-
C (1 bit): The flag and its value MUST be ignored.
-
F - bit5 (1 bit): Not used; set to 0 and ignored.
-
G - bit6 (1 bit): Not used; set to 0 and ignored.
-
H - bit7 (1 bit): Not used; set to 0 and ignored.