Issue 11072: Interpreting Liveliness Heartbeats (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:
For better performance and simpler reliability, a liveliness heartbeat should be allowed to be a liveliness-only message without heartbeat semantics.  As subclassed from a heartbeat, a liveliness heartbeat may trigger an ACKNACK response; to be a liveliness-only message, no ACKNACKs should be triggered.  To enable this, setting the final flag should not trigger ACKNACKs.     

Resolution:
A liveliness heartbeat with final-flag set must not trigger any ACKNACKs.

Revised Text:
Append to 8.4.2.3.2:

The response is not required when a liveliness HEARTBEAT has both liveliness and final flags set to indicate it is a liveliness-only message.

Revise statechart 8.24:

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

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

Interpreting Liveliness Heartbeats

Source:
Real-Time Innovations, Inc. (Ken Brophy, ken@rti.com)
Summary:
For better performance and simpler reliability, a liveliness heartbeat should be allowed to be a liveliness-only message without heartbeat semantics.  As subclassed from a heartbeat, a liveliness heartbeat may trigger an ACKNACK response; to be a liveliness-only message, no ACKNACKs should be triggered.  To enable this, setting the final flag should not trigger ACKNACKs.     

Resolution:
A liveliness heartbeat with final-flag set must not trigger any ACKNACKs.

Revised Text:
Append to 8.4.2.3.2:

The response is not required when a liveliness HEARTBEAT has both liveliness and final flags set to indicate it is a liveliness-only message.

Revise statechart 8.24:
 >>SEE ATTACHED issue11072.doc