-
Key: DDS-61
-
Legacy Issue Number: 6767
-
Status: closed
-
Source: Real-Time Innovations ( Dr. Gerardo Pardo-Castellote, Ph.D.)
-
Summary:
Ref-35 Entity_specialization_set_get_qos
The specification shows this operation as being abstract on the
base-class (Entity) and says that it will be overridden by each
specialization (Section 2.1.2.1.1.2). This is consistent with the PSM.However, the get_qos/set_qos operations are not mentioned in the
tables and text that that describe the DomainParticipant (section
2.1.2.2.1.Also for the specialized Entity classes, the operations are not
mantioned on the class table but do appear in the text that describes
the table. This applies to Topic (section 2.1.2.3.2), Publisher
(section 2.1.2.4.1), DataWriter (section 2.1.2.4.2), Subscriber
(section 2.1.2.5.2), and DataReader (section 2.1.2.5.3).**PROPOSAL**
In order to avoid ambiguity, the get_qos/set_qos operation should
appear explicitly in all the aforementioned sections. -
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 — Entity specialization of set/get qos/listener
- Key: DDS-61
- OMG Task Force: Data Distribution Service FTF