The Lab

Expand all   Collapse all

Versions Compared

Old Version 44

changes.mady.by.user Matthew Whitaker

Saved on

compared with

New Version 45

changes.mady.by.user Matthew Whitaker

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.


MaxTx

For inbound Heartbeat and TestRequest messages sent by the client, the FH will allow a fixed maximum allowed message transmission time (MaxTx), currently set to one second, before treating the message as 'missed'. This is used to allow for some degree of hysteresis WRT message delivery latencies.

The client may specify it's own MaxTx value and logic when monitoring inbound messages sent by the FH.

In both cases only the local clock is used as reference.


Heartbeats

Once the MFAPI Client has successfully established a session with the Whisperer Feed Handler (i.e. on dispatch of the first Heartbeat message in response to the end of synchronisation TestRequest), subsequent Heartbeat messages are sent by each party at the interval specified by the MFAPI client in it's Logon message.

...