Page History
...
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Message Persistence
The table below specifies what messages are to be persisted and resent when necessary, as opposed to being gap-filled:
...
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Session Monitoring
Active sessions are monitored at the application level by each party via Heartbeat and TestRequest messages. Indications of problems must result in the monitoring party aborting the session.
...
Once the MFAPI Client has successfully established a session with the Whisperer Feed Handler , Heartbeat (i.e. on dispatch of the first Heartbeat message in response to the end of synchronisation TestRequest), subsequent Heartbeat messages are sent by both parties each party at the interval specified by the MFAPI client in it's Logon message.
...
A heartbeat is deemed to have been missed if it is not received within HeartBtInt + MaxTx seconds and must result in the monitoring party issuing a TestRequest.
...
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
| Note | ||
|---|---|---|
| ||
User fails to respond to a testrequest and sends no messages Same but in the opposite direction. |
...
Overview
Content Tools