-
Key: DDS-130
-
Legacy Issue Number: 6836
-
Status: closed
-
Source: Real-Time Innovations ( Dr. Gerardo Pardo-Castellote, Ph.D.)
-
Summary:
Ref-101 Move_sample_lost_status_to_datareader
Section 2.1.4.2 shows in a table that SAMPLE_LOST_STATUS is on the
Subscriber. It would make more sense to have it on the Datareader. It
is not as useful to the application to know that samples have been
lost for DataReaders belonging to the Subscriber as it would be to
know which DataReaders they affected.When we first specified this it was thought that it would be hard to
implement as a status on the DataReader because, given that the
samples are lost, it would not be clear which DataReader they
affect. As it turns out the anticipated implementation difficulties
are not there.**PROPOSAL**
Remove the SAMPLE_LOST_STATUS from the status of the Subscriber and
add it to that of the DataReader in the table in 2.1.4.2Also modify the PIM in section 2.1.2.5.2 and the PSM in section 2.2.3
moving the get_sample_lost_status operation from Subscriber to
DataReader -
Reported: DDS 1.0b1 — Tue, 23 Dec 2003 05:00 GMT
-
Disposition: Resolved — DDS 1.0
-
Disposition Summary:
see below
-
Updated: Fri, 6 Mar 2015 20:58 GMT
DDS — DDS ISSUE# 37] SAMPLE_LOST_STATUS on DataReader
- Key: DDS-130
- OMG Task Force: Data Distribution Service FTF