-
Key: DDSIRTP2-9
-
Legacy Issue Number: 11037
-
Status: closed
-
Source: Real-Time Innovations ( Mr. Kenneth Brophy)
-
Summary:
Source:
Real-Time Innovations, Inc. (Ken Brophy, ken@rti.com)
Summary:
The requirement contained in Section 8.4.2.3.3 is too restrictive and doesn't specify when resources can be reclaimed. If all Readers have acknowledged a sample, the Writer should be allowed to reclaim that sample's resources. Also, if a Reader NACKs a sample it has already ACKed, and the Writer is still able to provide a repair, it should.
Resolution:
Allow Writer to reclaim resources and send repairs if possible.
Revised Text:
Add the paragraph to the end of Section 8.4.2.3.3:Once a Writer has received positive acknowledgement from all Readers, the Writer can reclaim any associated resources. However, if a Writer receives a negative acknowledgement to a previously positively acknowledged sample, and the Writer can still service the request, the Writer should send the sample.
-
Reported: DDSI-RTPS 2.0b1 — Wed, 23 May 2007 04:00 GMT
-
Disposition: Resolved — DDSI-RTPS 2.0
-
Disposition Summary:
see above
-
Updated: Fri, 6 Mar 2015 20:58 GMT
DDSIRTP2 — Clarify interoperability requirement 8.4.2.3.3
- Key: DDSIRTP2-9
- OMG Task Force: DDS Interoperability FTF