-
Key: DDS11-68
-
Legacy Issue Number: 8423
-
Status: closed
-
Source: Real-Time Innovations ( Dr. Gerardo Pardo-Castellote, Ph.D.)
-
Summary:
In the description of DataWriter::unregister in section 2.1.2.4.2.7 it says that if an instance is unregistered via a call to DataWriter::unregister, a matched DataReader will get an indication that its LIVELINESS_CHANGED status has changed.
However, unregister refers to an instance; the LIVELINESS_CHANGED status is based on the liveliness of a DataWriter, not an instance.Proposed Resolution:
Instead the specification should state that the DataReader will receive a sample with a NOT_ALIVE_NO_WRITERS instance state.Proposed Revised Text:
The sentence:
DataReader objects that are reading the instance will eventually get an indication that their LIVELINESS_CHANGED status (as defined in Section 2.1.4.1) has changed.
Â…should be rewritten:
DataReader objects that are reading the instance will eventually receive a sample with a NOT_ALIVE_NO_WRITERS instance state if no other DataWriter objects are writing the instance. -
Reported: DDS 1.0 — Tue, 1 Mar 2005 05:00 GMT
-
Disposition: Resolved — DDS 1.1
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 20:58 GMT
DDS11 — Incorrect reference to LIVELINESS_CHANGED in DataWriter::unregister
- Key: DDS11-68
- OMG Task Force: Data Distribution Service RTF