Issue 11071: Reader-side Heartbeat response suppression (data-distribution-interop-rtf)
Source: Real-Time Innovations (Mr. Kenneth Brophy, ken(at)rti.com)
Nature: Uncategorized Issue
Severity: 
Summary: Source:
Real-Time Innovations, Inc. (Ken Brophy, ken@rti.com)
Summary:
The specification does not prevent multiple Heartbeats from arriving in rapid succession.  For example, the piggyback heartbeat of a repair message may immediately be followed by a periodic wildcard heartbeat.  In order to prevent duplicate repair sessions, the specification should define heartbeat suppression on the reader's side.  This heartbeat response suppression should be handled by a reader attribute that controls the duration for which duplicate heartbeats would be ignored.

Resolution:
Add reader attribute, heartbeatSuppressionDuration, that defines the duration in which received heartbeats are suppressed from triggering duplicate ACKNACKs.

Revised Text:
Revised figure 8.21:

Resolution: 
Revised Text: 
Actions taken:
May 25, 2007: received issue
Discussion: 

End of Annotations:=====
s is issue # 11071

Reader-side Heartbeat response suppression

Source:
Real-Time Innovations, Inc. (Ken Brophy, ken@rti.com)
Summary:
The specification does not prevent multiple Heartbeats from arriving in rapid succession.  For example, the piggyback heartbeat of a repair message may immediately be followed by a periodic wildcard heartbeat.  In order to prevent duplicate repair sessions, the specification should define heartbeat suppression on the reader's side.  This heartbeat response suppression should be handled by a reader attribute that controls the duration for which duplicate heartbeats would be ignored.

Resolution:
Add reader attribute, heartbeatSuppressionDuration, that defines the duration in which received heartbeats are suppressed from triggering duplicate ACKNACKs.

Revised Text:
Revised figure 8.21:

>>SEE ATTACHED FILE issue11071.doc