Static Public Attributes | |
static final PublishModeQosPolicyKind | SYNCHRONOUS_PUBLISH_MODE_QOS |
Indicates to send data synchronously. | |
static final PublishModeQosPolicyKind | ASYNCHRONOUS_PUBLISH_MODE_QOS |
Indicates to send data asynchronously. |
final PublishModeQosPolicyKind SYNCHRONOUS_PUBLISH_MODE_QOS [static] |
Indicates to send data synchronously.
If com.rti.dds.infrastructure.DataWriterProtocolQosPolicy.push_on_write is true, data is sent immediately in the context of com.rti.dds.topic.example.FooDataWriter.write.
As data is sent immediately in the context of the user thread, no flow control is applied.
[default] for com.rti.dds.publication.DataWriter
final PublishModeQosPolicyKind ASYNCHRONOUS_PUBLISH_MODE_QOS [static] |
Indicates to send data asynchronously.
Configures the com.rti.dds.publication.DataWriter to delegate the task of data transmission to a separate publishing thread. The com.rti.dds.topic.example.FooDataWriter.write call does not send the data, but instead schedules the data to be sent later by its associated com.rti.dds.publication.Publisher.
Each com.rti.dds.publication.Publisher uses its dedicated publishing thread (com.rti.dds.publication.PublisherQos.asynchronous_publisher) to send data for all its asynchronous DataWriters. For each asynchronous DataWriter, the associated com.rti.dds.publication.FlowController determines when the publishing thread is allowed to send the data.
com.rti.dds.publication.DataWriter.wait_for_asynchronous_publishing and com.rti.dds.publication.Publisher.wait_for_asynchronous_publishing enable you to determine when the data has actually been sent.
Note: com.rti.dds.infrastructure.DataWriterProtocolQosPolicy.push_on_write must be TRUE for Asynchronous DataWriters. Otherwise, samples will never be sent.
com.rti.dds.infrastructure.HistoryQosPolicy
com.rti.dds.publication.DataWriter.wait_for_asynchronous_publishing
com.rti.dds.publication.Publisher.wait_for_asynchronous_publishing
Transport.Property_t.gather_send_buffer_count_max