PublishModeQosPolicy Class Reference
[PUBLISH_MODE]

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...

Inheritance diagram for PublishModeQosPolicy:

List of all members.

Public Attributes
PublishModeQosPolicyKind	kind
	Publishing mode.
String	flow_controller_name
	Name of the associated flow controller.

---

Detailed Description

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.

The publishing mode of a com.rti.dds.publication.DataWriter determines whether data is written synchronously in the context of the user thread when calling com.rti.dds.topic.example.FooDataWriter.write or asynchronously in the context of a separate thread internal to the middleware.

Each com.rti.dds.publication.Publisher spawns a single asynchronous publishing thread (com.rti.dds.infrastructure.AsynchronousPublisherQosPolicy.thread) to serve all its asynchronous com.rti.dds.publication.DataWriter instances.

See also:

com.rti.dds.infrastructure.AsynchronousPublisherQosPolicy

com.rti.dds.infrastructure.HistoryQosPolicy

com.rti.dds.publication.FlowController

Entity:

com.rti.dds.publication.DataWriter

Properties:

RxO = N/A
Changeable = NO

Usage

The fastest way for RTI Connext to send data is for the user thread to execute the middleware code that actually sends the data itself. However, there are times when user applications may need or want an internal middleware thread to send the data instead. For instance, to send large data reliably, you must use an asynchronous thread.

When data is written asynchronously, a com.rti.dds.publication.FlowController, identified by flow_controller_name, can be used to shape the network traffic. Shaping a data flow usually means limiting the maximum data rates at which the middleware will send data for a com.rti.dds.publication.DataWriter. The flow controller will buffer any excess data and only send it when the send rate drops below the maximum rate. The flow controller's properties determine when the asynchronous publishing thread is allowed to send data and how much.

Asynchronous publishing may increase latency, but offers the following advantages:

- The com.rti.dds.topic.example.FooDataWriter.write call does not make any network calls and is therefore faster and more deterministic. This becomes important when the user thread is executing time-critical code.

- When data is written in bursts or when sending large data types as multiple fragments, a flow controller can throttle the send rate of the asynchronous publishing thread to avoid flooding the network.

- Asynchronously written samples for the same destination will be coalesced into a single network packet which reduces bandwidth consumption.

The maximum number of samples that will be coalesced depends on Transport.Property_t.gather_send_buffer_count_max (each sample requires at least 2-4 gather-send buffers). Performance can be improved by increasing Transport.Property_t.gather_send_buffer_count_max. Note that the maximum value is operating system dependent.

The middleware must queue samples until they can be sent by the asynchronous publishing thread (as determined by the corresponding com.rti.dds.publication.FlowController). The number of samples that will be queued is determined by the com.rti.dds.infrastructure.HistoryQosPolicy. When using HistoryQosPolicyKind.KEEP_LAST_HISTORY_QOS, only the most recent com.rti.dds.infrastructure.HistoryQosPolicy.depth samples are kept in the queue. Once unsent samples are removed from the queue, they are no longer available to the asynchronous publishing thread and will therefore never be sent.

---

Member Data Documentation

PublishModeQosPolicyKind kind

Publishing mode.

[default] PublishModeQosPolicyKind.SYNCHRONOUS_PUBLISH_MODE_QOS

String flow_controller_name

Name of the associated flow controller.

NULL value or zero-length string refers to FlowController.DEFAULT_FLOW_CONTROLLER_NAME.

See also:

com.rti.dds.domain.DomainParticipant.create_flowcontroller

FlowController.DEFAULT_FLOW_CONTROLLER_NAME

FlowController.FIXED_RATE_FLOW_CONTROLLER_NAME

FlowController.ON_DEMAND_FLOW_CONTROLLER_NAME

[default] FlowController.DEFAULT_FLOW_CONTROLLER_NAME