Page History
...
- 52/SendingTime
- 122/OrigSendingTime (resends only)
- 60/TransactTime (Quote, MassQuote, ExecutionReport)
Logon
Client Logon message contains the correct values for:
- HeartBtInt
- SessionType = RFS
- Username/Password - correct
- VenueName = ?/?
Session Synchronisation
Client Logon next-expected = MF actual
...
MF LogonResponse next-expected > Client actual
Correctly disconnects.
Logoff
All client sessions must be terminated gracefully.
Client-Initiated Logoff
Client may only issue Logoff when no Venue session is active.
Client waits for reciprocal Logoff message from MF.
MF-Initiated (e.g. on weekend restart)
Client responds to MF-issued Logoff message with reciprocal Logoff.
Session Monitoring
Client Heartbeats
...
- Correctly timesout and sends TestRequest.
- Correctly timesout and sends Logout.
- Correctly timesout and disconnects.
TestRequest Handling
The Client sends a Heartbeat message in response to every MF TestRequest : send Heartbeat responsemessage received.
Venue Connectivity
The sequencing matters.
UserRequest
...
(LogOnUser)
Client directs MF to connect to Venue.
Message only sent when the client is not currently logged on.
ErrorReport
Client receives MF notification of any connectivity problems and planned next action.
UserNotification (LoggedOn)
Client is notified when Venue connectivity is established.
UserRequest (LogOffUser)
Client directs MF to disconnect from Venue.
Message may be sent:
- When MF is in a connection-attempt cycle, after a prior UserRequest (LogOnUser)
- When client has been notified that they have been logged on via UserNotification (LoggedOn).
UserNotification (LoggedOff)
Maker RFS Workflow
-focus on _outbound_ message correctness.
...