Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
| faq:resend_request [2025/01/16 13:30] – rob | faq:resend_request [2025/01/16 13:32] (current) – rob | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Resend Request ===== | ===== Resend Request ===== | ||
| - | === Message Range Replay === | + | ===== Message Range Replay ===== |
| + | |||
| With the Resend Request message, a receiving application asks for the retransmission of previously sent messages. The previously sent messages span over an input range of sequence numbers. The input range is specified with **BeginSeqNo** (Tag 7) and **EndSeqNo** (Tag 16). To request only one message, **BeginSeqNo** is set equal to **EndSeqNo**. The specification of zero (0) for **EndSeqNo** indicates that the requested range would end with the sent message of highest sequence number (i.e. the last message sent). | With the Resend Request message, a receiving application asks for the retransmission of previously sent messages. The previously sent messages span over an input range of sequence numbers. The input range is specified with **BeginSeqNo** (Tag 7) and **EndSeqNo** (Tag 16). To request only one message, **BeginSeqNo** is set equal to **EndSeqNo**. The specification of zero (0) for **EndSeqNo** indicates that the requested range would end with the sent message of highest sequence number (i.e. the last message sent). | ||
| Line 12: | Line 13: | ||
| A proper response for a Resend Request includes all the application messages (with the exception of [[MarketData Snapshot FullRefresh|MarketData Snapshot]] and [[Security Definition|Security Definition]]) but no administrative messages (with the exception of [[Reject|Reject]]). The resending application may decide not to resend specific messages (e.g. NewOrder) if it considers it risky or the messages would be resent out of an acceptable time window. All messages (resent by the application honoring the Resend Request) must be labeled as a Possible Duplicate (i.e. Tag 43=Y). The T4 FIX API will honor all Possible Duplicates received from the client. If message gaps exist in the resend message lot, [[Sequence Reset|Sequence Reset]] messages can be received to fill the sequence number gap. This is a common occurrence when administrative messages are excluded from the resend lot. | A proper response for a Resend Request includes all the application messages (with the exception of [[MarketData Snapshot FullRefresh|MarketData Snapshot]] and [[Security Definition|Security Definition]]) but no administrative messages (with the exception of [[Reject|Reject]]). The resending application may decide not to resend specific messages (e.g. NewOrder) if it considers it risky or the messages would be resent out of an acceptable time window. All messages (resent by the application honoring the Resend Request) must be labeled as a Possible Duplicate (i.e. Tag 43=Y). The T4 FIX API will honor all Possible Duplicates received from the client. If message gaps exist in the resend message lot, [[Sequence Reset|Sequence Reset]] messages can be received to fill the sequence number gap. This is a common occurrence when administrative messages are excluded from the resend lot. | ||
| - | === Message Dictionary === | + | ===== Message Dictionary ===== |
| + | |||
| ^ Tag ^ Field Name ^ Req'd ^ Comments ^ | ^ Tag ^ Field Name ^ Req'd ^ Comments ^ | ||
| Line 20: | Line 22: | ||
| | | **[[Standard Trailer]]** | Y | | | | **[[Standard Trailer]]** | Y | | ||
| - | === Sample Messages === | + | ===== Sample Messages ===== |
| + | |||
| < | < | ||