-
Key: DDS12-15
-
Legacy Issue Number: 9492
-
Status: closed
-
Source: Real-Time Innovations ( Dr. Gerardo Pardo-Castellote, Ph.D.)
-
Summary:
Summary:
In Section 2.1.3.7 concerning the DEADLINE QoS, it is stated that if the QoS is set inconsistently, i.e. period is < minimum_separation of the TIME_BASED_FILTER QoS, the INCONSISTENT_POLICY status will change and any associated Listeners/WaitSets will be triggered.
There is no such status. Instead the set_qos() operation will error with return code INCONSISTENT_POLICY.Proposed Resolution:
Mention the return code instead.Proposed Revised Text:
Section 2.1.3.7 DEADLINE
Remove the last sentence in the section:
"An attempt to set these policies in
an inconsistent manner will cause the INCONSISTENT_POLICY status to change and any associated Listeners/WaitSets to be triggered." -
Reported: DDS 1.1 — Sun, 2 Apr 2006 05:00 GMT
-
Disposition: Resolved — DDS 1.2
-
Disposition Summary:
Mention the return code instead
-
Updated: Fri, 6 Mar 2015 20:58 GMT
DDS12 — Incorrect mention of INCONSISTENT_POLICY status
- Key: DDS12-15
- OMG Task Force: Data Distribution RTF 3