2.2.1.5.5 transactions Element

The transactions XML element represents file transfer statistics.

 <xs:element name="transactions">
   <xs:complexType>
     <xs:sequence>
       <xs:element name="recvdfiles"
         type="xs:long"
        />
       <xs:element name="backlogInbound"
         type="xs:long"
        />
       <xs:element name="backlogOutbound"
         type="xs:long"
        />
     </xs:sequence>
   </xs:complexType>
 </xs:element>

Child Elements

Element

Type

Description

recvdfiles

xs:long

MUST be the total number of new or updated files that are received by the server from other members since the DFS Replication service started.

backlogInbound

xs:long

MUST be the number of inbound backlogged transactions relative to the version vector that were provided as a parameter to the server. This number MUST be calculated by comparing the version of each file in the version vector that is sent by the client with the version of the file that exists on this computer. It MUST be calculated by counting the number of files whose version numbers are lower on this computer than on the caller's computer and counting the files that are present in the version vector but not on this computer.

The client is responsible for getting the version vector from another server that is participating in the replication group. The client MAY use the IServerHealthReport::GetReferenceVersionVectors or IServerHealthReport2::GetReferenceVersionVectors method to get this version vector from another server or use a different implementation-specific way of getting the version vectors.<8>

backlogOutbound

xs:long

MUST be the number of outbound backlogged transactions relative to the reference member. This number MUST be calculated by comparing the version of each file in the version vector that is sent by the caller's computer with the version of the file that exists on this computer. It is calculated by counting the number of files whose version numbers are higher on this computer than on the caller's computer and counting the files that are present on this computer but not in the version vector.

The client is responsible for getting the version vector from another server that is participating in the replication group. The client MAY use the IServerHealthReport::GetReferenceVersionVectors or IServerHealthReport2::GetReferenceVersionVectors method to get this version vector from another server or use a different implementation-specific way of getting the version vectors.<9>