Page History
...
- Line Arbitrage - the
MDSubFeedTypespecifies the UDP market data source for venues which utilise A/B circuits. - Gap Detection - in the event that a UDP message gap occurs, this is reported to the Client User immediately it is detected for each affected subscription, via the publication of a EmptyBook
MarketDatIncrementalRefreshmessage withMDFlags.IsSnapshotandMDFlags.GapDetectedboth set to TRUE. - Gap Recovery - the gap will be resolved by the Gateway utilising the venue's standard Late-joiner logic, and the next message will be a fresh Snapshot (typically, but not always, representing the full book). Thereafter Incrementals will be published as normal.
Orders
The Orders workflow is always normalised and consistently implements the state transition model as outlined in the diagram below. Where Venue events are absent, synthetic equivalents are generated by Whisperer in their place. These messages are easily discernible by reference to the TradingFlags.IsSynthetic field.
| Info | ||
|---|---|---|
| ||
| It's worth remembering that while all inbound messages will adhere to the same state transition model, there will necessarily be Venue-specific variation in whether and how outbound ExecutionAck messages are handled. |
Order State Transition Diagram
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Order Submission and Modification
...
Overview
Content Tools