-
Key: DDS11-57
-
Legacy Issue Number: 8395
-
Status: closed
-
Source: Real-Time Innovations ( Dr. Gerardo Pardo-Castellote, Ph.D.)
-
Summary:
The specification does not state what the valid range of the transport priority values is, now does it state whether higher or lower values correspond to higher priorities.
Proposed Resolution:
Stipulate that the range of TransportPriorityQosPolicy::value is the entire range of a 32 bit signed integer. Larger numbers indicate higher priority. However, the precise interpretation of the value chosen is transport- and implementation-dependent.Proposed Revised Text:
The second paragraph of section 2.1.3.14 contains the sentence:
"As this is specific to each transport it is not possible to define the behavior generically."This sentence should be rewritten as follows:
"Any value within the range of a 32-bit signed integer may be chosen; higher values indicate higher priority. However, any further interpretation of this policy is specific to a particular transport and a particular implementation of the Service. For example, a particular transport is permitted to treat a range of priority values as equivalent to one another." -
Reported: DDS 1.0 — Mon, 28 Feb 2005 05:00 GMT
-
Disposition: Resolved — DDS 1.1
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 20:58 GMT
DDS11 — TransportPriority QoS range does not specify high/low priority values
- Key: DDS11-57
- OMG Task Force: Data Distribution Service RTF