RTI Connext .NET API (legacy)
Version 6.1.1
|
<<extension>> Specifies how RTI Connext sends application data on the network. This QoS policy can be used to tell RTI Connext to use its own thread to send data, instead of the user thread. More...
Classes | |
class | DDS::PublishModeQosPolicy |
Specifies how RTI Connext sends application data on the network. This QoS policy can be used to tell RTI Connext to use its own thread to send data, instead of the user thread. More... | |
Enumerations | |
enum | DDS::PublishModeQosPolicyKind : UINT32 { DDS::PublishModeQosPolicyKind::SYNCHRONOUS_PUBLISH_MODE_QOS, DDS::PublishModeQosPolicyKind::ASYNCHRONOUS_PUBLISH_MODE_QOS } |
Kinds of publishing mode. More... | |
Functions | |
static System::String ^ | DDS::PublishModeQosPolicy::get_publishmode_qos_policy_name () |
Stringified human-readable name for DDS::PublishModeQosPolicy. More... | |
Properties | |
static System::Int32 | DDS::FilterSampleInfo::PRIORITY_UNDEFINED [get] |
Initializer value for DDS::PublishModeQosPolicy::priority and/or DDS::ChannelSettings_t::priority. More... | |
static System::Int32 | DDS::FilterSampleInfo::PRIORITY_AUTOMATIC [get] |
Constant value for DDS::PublishModeQosPolicy::priority and/or DDS::ChannelSettings_t::priority. More... | |
<<extension>> Specifies how RTI Connext sends application data on the network. This QoS policy can be used to tell RTI Connext to use its own thread to send data, instead of the user thread.
|
strong |
Kinds of publishing mode.
Enumerator | |
---|---|
SYNCHRONOUS_PUBLISH_MODE_QOS | Indicates to send data synchronously. If DDS::DataWriterProtocolQosPolicy::push_on_write is true, data is sent immediately in the context of DDS::TypedDataWriter::write. As data is sent immediately in the context of the user thread, no flow control is applied. [default] for DDS::DataWriter |
ASYNCHRONOUS_PUBLISH_MODE_QOS | Indicates to send data asynchronously. Configures the DDS::DataWriter to delegate the task of data transmission to a separate publishing thread. The DDS::TypedDataWriter::write call does not send the data, but instead schedules the data to be sent later by its associated DDS::Publisher. Each DDS::Publisher uses its dedicated publishing thread (DDS::PublisherQos::asynchronous_publisher) to send data for all its asynchronous DataWriters. For each asynchronous DataWriter, the associated DDS::FlowController determines when the publishing thread is allowed to send the data. DDS::DataWriter::wait_for_asynchronous_publishing and DDS::Publisher::wait_for_asynchronous_publishing enable you to determine when the data has actually been sent. |
|
inlinestatic |
Stringified human-readable name for DDS::PublishModeQosPolicy.
|
staticget |
Initializer value for DDS::PublishModeQosPolicy::priority and/or DDS::ChannelSettings_t::priority.
When assigned this value, the publication priority of the data writer, or channel of a multi-channel data writer, will be set to the lowest possible value. For muilti-channel data writers, if either the data writer or channel priority is NOT set to this value, then the publication priority of the entity will be set to the defined value.
|
staticget |
Constant value for DDS::PublishModeQosPolicy::priority and/or DDS::ChannelSettings_t::priority.
When assigned this value, the publication priority of the data writer, or channel of a multi-channel data writer, will be set to the largest priority value of any sample currently queued for publication by the data writer or data writer channel.