Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| faq:heartbeat [2025/01/16 20:21] – rob | faq:heartbeat [2025/01/16 20:22] (current) – [Session Integrity] rob | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| Heartbeats provide (application-level) connectivity during a FIX session. The heartbeat message maintains the communication link when transactional messages (e.g. trading order routing message) are not received. Under normal conditions, the client and T4 FIX API server will interchange heartbeats at the pre-determined periodic interval (30 seconds). Heartbeats are acknowledged by the counterparty through the generation of a subsequent " | Heartbeats provide (application-level) connectivity during a FIX session. The heartbeat message maintains the communication link when transactional messages (e.g. trading order routing message) are not received. Under normal conditions, the client and T4 FIX API server will interchange heartbeats at the pre-determined periodic interval (30 seconds). Heartbeats are acknowledged by the counterparty through the generation of a subsequent " | ||
| - | When no message is received within the periodic interval, a heartbeat time-out condition is encountered. Thereafter, a heartbeat is sent to the non-responding party. Upon further unresponsiveness, | + | When no message is received within the periodic interval, a heartbeat time-out condition is encountered. Thereafter, a heartbeat is sent to the non-responding party. Upon further unresponsiveness, |
| Please note that regardless of time-out conditions, Test Requests can be sent by either party at any time. Correspondingly, | Please note that regardless of time-out conditions, Test Requests can be sent by either party at any time. Correspondingly, | ||