Issue 6851: DDS ISSUE# 51] Avoid use of dynamic memory for manipulating QoS (data-distribution-ftf)
Source: Real-Time Innovations (Dr. Gerardo Pardo-Castellote, Ph.D., gerardo(at)rti.com)
Nature: Uncategorized Issue
Severity: 
Summary: Ref-122 Make_incompatible_qos_fixed_size


The structures RequestedIncompatibleQosStatus and
RequestedIncompatibleQosStatus each contain a sequence listing each
QoS and the corresponding count.


However given that we have explicitly enumerated all the QoS policies
it would be far simpler to replace this hard-to-use sequence with the
actual counts for each QoS


One possibility would be to Replace this "policies" sequence with
explicit count for each QoS. Anotehr possibility would be to use the
mask. To state which QoS are incompatible but loose the count.


***PROPOSAL***


No concrete proposal yet

Resolution: 
Revised Text: 
Actions taken:
December 23, 2003: received issue
Discussion: 
Resolution: 
The FTF recognizes it would be desirable to find a way to not force the use of dynamic memory. However, the FTF could not agree on a resolution to this issue and agreed to defer the issue for a future revision.

End of Annotations:=====
 ISSUE# 51] Avoid use of dynamic memory for manipulating QoS


***Ref-122 Make_incompatible_qos_fixed_size


The structures RequestedIncompatibleQosStatus and
RequestedIncompatibleQosStatus each contain a sequence listing each
QoS and the corresponding count.


However given that we have explicitly enumerated all the QoS policies
it would be far simpler to replace this hard-to-use sequence with the
actual counts for each QoS


One possibility would be to Replace this "policies" sequence with
explicit count for each QoS. Anotehr possibility would be to use the
mask. To state which QoS are incompatible but loose the count.


***PROPOSAL***


No concrete proposal yet

[OMG ISSUE# 6851, DDS# 51] Avoid use of dynamic memory for manipulating QoS
Ref-122 Make_incompatible_qos_fixed_size
The structures RequestedIncompatibleQosStatus and RequestedIncompatibleQosStatus each contain a sequence listing each QoS and the corresponding count.
However given that we have explicitly enumerated all the QoS policies it would be far simpler to replace this hard-to-use sequence with the actual counts for each QoS
One possibility would be to Replace this .policies. sequence with explicit count for each QoS. Another possibility would be to use the mask. To state which QoS are incompatible but loose the count.
***PROPOSAL***
No concrete proposal yet