ddsf:public:guidebook:06_append:02_quality_of_service:transport_priority
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
ddsf:public:guidebook:06_append:02_quality_of_service:transport_priority [2021/07/14 15:54] murphy ↷ Links adapted because of a move operation |
ddsf:public:guidebook:06_append:02_quality_of_service:transport_priority [2021/07/14 15:55] (current) murphy ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| [[ddsf:public:guidebook:06_append:02_quality_of_service:start|return to the Quality of Service (QoS) Parameters ]] | [[ddsf:public:guidebook:06_append:02_quality_of_service:start|return to the Quality of Service (QoS) Parameters ]] | ||
| - | The [[ddsf:private:guidebook:06_append:glossary:t:transport_priority|TRANSPORT_PRIORITY]] [[ddsf:public:guidebook:06_append:glossary:q:quality_of_service_qos_policies|QoS]] policy allows the application to take advantage of transports capable of sending messages with different priorities. | + | The [[ddsf:public:guidebook:06_append:glossary:t:transport_priority|TRANSPORT_PRIORITY]] [[ddsf:public:guidebook:06_append:glossary:q:quality_of_service_qos_policies|QoS]] policy allows the application to take advantage of transports capable of sending messages with different priorities. |
| This policy is considered a hint. The policy depends on the ability of the underlying transports to set a priority on the messages they send. Any value within the range of a [[ddsf:public:guidebook:06_append:glossary:0-9: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. It is expected that during transport configuration the application would provide a mapping between the values of the TRANSPORT_PRIORITY set on ''DataWriter'' and the values meaningful to each transport. This mapping would then be used by the infrastructure when propagating the data written by the ''DataWriter''. | This policy is considered a hint. The policy depends on the ability of the underlying transports to set a priority on the messages they send. Any value within the range of a [[ddsf:public:guidebook:06_append:glossary:0-9: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. It is expected that during transport configuration the application would provide a mapping between the values of the TRANSPORT_PRIORITY set on ''DataWriter'' and the values meaningful to each transport. This mapping would then be used by the infrastructure when propagating the data written by the ''DataWriter''. | ||
ddsf/public/guidebook/06_append/02_quality_of_service/transport_priority.1626292441.txt.gz · Last modified: 2021/07/14 15:54 by murphy
