-
Key: DDSJAVA-34
-
Legacy Issue Number: 16543
-
Status: closed
-
Source: ZettaScale Technology ( Angelo Corsaro, PhD.)
-
Summary:
The dds-psm-java currently passes statuses via collections. However this
does not make it neither efficient nor simple to represent collections
of related statuses, such as the Read Status, etc.[Resolution]
The suggestion is to add a ReadState as currently present on the dds-psm-cxx
to simplify the API and make it simpler to support the most common use cases. -
Reported: DDS-Java 1.0b1 — Wed, 7 Sep 2011 04:00 GMT
-
Disposition: Resolved — DDS-Java 1.0b2
-
Disposition Summary:
[Angelo] The suggestion is to add a ReadState as currently present on the DDS-PSM-Cxx to simplify the API and make it simpler to support the most common use cases.
[Rick] This issue is unclear to me. I take it that this issue is not referring to actual Status objects. The reference to what is called “Read Status” or “Read State” and to DDS-PSM-Cxx makes me think it is related to the DDS-PSM-Cxx class called “ReaderState”, which encapsulates sets of Sample States, View States, and Instance States. This change is already proposed in DDS-PSM-Java as part of the proposed resolution to issue #16321.
Resolution:
Merge this issue with issue #16321.
Disposition: Merge with issue #16321 -
Updated: Fri, 6 Mar 2015 20:58 GMT
DDSJAVA — Statuses API shoud be improved and made typesafe
- Key: DDSJAVA-34
- OMG Task Force: Java 5 Language PSM for DDS 1.0 FTF