...

A constant value of 17997 must always be assigned to this field, this corresponds to an on-the-wire byte representation of "MF":

• The MF Reference API populates this value on the Client's behalf in all messages sent to the FH.
• If a Client implementation should not use the Reference API, then it must implement it's own mechanism to ensure that this value is always populated.
• The FH will ensure that this is populated in every message sent to the Client.
• The FH will validate every message received from the Client.

Message Length

The standard header doesn't include this and its absence prevents backward compatibility in the general case.

Message Sequence Number

Sending Time

Hops Group

MarketFactory provides a detailed breakdown of inbound message latencies from the Venue to the Client via the NoHops group included in all Application-level messages. This group contains the following fields:

• • HopRefID - this is the specific sequence number of the originating Venue message.
  • HopSendingTime - this is the Venue clock time that the Venue message was sent.
  • HopNetworkTime - this is the MF clock time that the Venue message was received by MF hardware. Solarflare is used for this purpose.
  • HopArrivalTime - this is the MF clock time that the Venue message was received in the Whisperer Enterprise Feed Handler application.

Client application software, Corvil and other network analysers can use these fields to in combination with measurements of arrival time in the client network to build up a multihop view of the latency.