Classes | |
| interface | FlowController |
| <<interface>> A flow controller is the object responsible for shaping the network traffic by determining when attached asynchronous com.rti.dds.publication.DataWriter instances are allowed to write data. More... | |
| class | FlowControllerProperty_t |
| Determines the flow control characteristics of the com.rti.dds.publication.FlowController. More... | |
| class | FlowControllerSchedulingPolicy |
| Kinds of flow controller scheduling policy. More... | |
| class | FlowControllerTokenBucketProperty_t |
| com.rti.dds.publication.FlowController uses the popular token bucket approach for open loop network flow control. The flow control characteristics are determined by the token bucket properties. More... | |
Variables | |
| static final String | DEFAULT_FLOW_CONTROLLER_NAME |
| [default] Special value of com.rti.dds.infrastructure.PublishModeQosPolicy.flow_controller_name that refers to the built-in default flow controller. | |
| static final String | FIXED_RATE_FLOW_CONTROLLER_NAME |
| Special value of com.rti.dds.infrastructure.PublishModeQosPolicy.flow_controller_name that refers to the built-in fixed-rate flow controller. | |
| static final String | ON_DEMAND_FLOW_CONTROLLER_NAME |
| Special value of com.rti.dds.infrastructure.PublishModeQosPolicy.flow_controller_name that refers to the built-in on-demand flow controller. | |
com.rti.dds.publication.FlowController provides the network traffic shaping capability to asynchronous com.rti.dds.publication.DataWriter instances. For use cases and advantages of publishing asnychronously, please refer to com.rti.dds.infrastructure.PublishModeQosPolicy of com.rti.dds.publication.DataWriterQos.
final String DEFAULT_FLOW_CONTROLLER_NAME [static, inherited] |
[default] Special value of com.rti.dds.infrastructure.PublishModeQosPolicy.flow_controller_name that refers to the built-in default flow controller.
RTI Connext provides several built-in com.rti.dds.publication.FlowController for use with an asynchronous com.rti.dds.publication.DataWriter. The user can choose to use the built-in flow controllers and optionally modify their properties or can create a custom flow controller.
By default, flow control is disabled. That is, the built-in FlowController.DEFAULT_FLOW_CONTROLLER_NAME flow controller does not apply any flow control. Instead, it allows data to be sent asynchronously as soon as it is written by the com.rti.dds.publication.DataWriter.
Essentially, this is equivalent to a user-created com.rti.dds.publication.FlowController with the following com.rti.dds.publication.FlowControllerProperty_t settings:
- com.rti.dds.publication.FlowControllerProperty_t.scheduling_policy = FlowControllerSchedulingPolicy.EDF_FLOW_CONTROLLER_SCHED_POLICY
- com.rti.dds.publication.FlowControllerProperty_t.token_bucket max_tokens = ResourceLimitsQosPolicy.LENGTH_UNLIMITED
- com.rti.dds.publication.FlowControllerProperty_t.token_bucket tokens_added_per_period = ResourceLimitsQosPolicy.LENGTH_UNLIMITED
- com.rti.dds.publication.FlowControllerProperty_t.token_bucket tokens_leaked_per_period = 0
- com.rti.dds.publication.FlowControllerProperty_t.token_bucket period = 1 second
- com.rti.dds.publication.FlowControllerProperty_t.token_bucket bytes_per_token = ResourceLimitsQosPolicy.LENGTH_UNLIMITED
final String FIXED_RATE_FLOW_CONTROLLER_NAME [static, inherited] |
Special value of com.rti.dds.infrastructure.PublishModeQosPolicy.flow_controller_name that refers to the built-in fixed-rate flow controller.
RTI Connext provides several builtin com.rti.dds.publication.FlowController for use with an asynchronous com.rti.dds.publication.DataWriter. The user can choose to use the built-in flow controllers and optionally modify their properties or can create a custom flow controller.
The built-in FlowController.FIXED_RATE_FLOW_CONTROLLER_NAME flow controller shapes the network traffic by allowing data to be sent only once every second. Any accumulated samples destined for the same destination are coalesced into as few network packets as possible.
Essentially, this is equivalent to a user-created com.rti.dds.publication.FlowController with the following com.rti.dds.publication.FlowControllerProperty_t settings:
- com.rti.dds.publication.FlowControllerProperty_t.scheduling_policy = FlowControllerSchedulingPolicy.EDF_FLOW_CONTROLLER_SCHED_POLICY
- com.rti.dds.publication.FlowControllerProperty_t.token_bucket max_tokens = ResourceLimitsQosPolicy.LENGTH_UNLIMITED
- com.rti.dds.publication.FlowControllerProperty_t.token_bucket tokens_added_per_period = ResourceLimitsQosPolicy.LENGTH_UNLIMITED
- com.rti.dds.publication.FlowControllerProperty_t.token_bucket tokens_leaked_per_period = ResourceLimitsQosPolicy.LENGTH_UNLIMITED
- com.rti.dds.publication.FlowControllerProperty_t.token_bucket period = 1 second
- com.rti.dds.publication.FlowControllerProperty_t.token_bucket bytes_per_token = ResourceLimitsQosPolicy.LENGTH_UNLIMITED
final String ON_DEMAND_FLOW_CONTROLLER_NAME [static, inherited] |
Special value of com.rti.dds.infrastructure.PublishModeQosPolicy.flow_controller_name that refers to the built-in on-demand flow controller.
RTI Connext provides several builtin com.rti.dds.publication.FlowController for use with an asynchronous com.rti.dds.publication.DataWriter. The user can choose to use the built-in flow controllers and optionally modify their properties or can create a custom flow controller.
The built-in FlowController.ON_DEMAND_FLOW_CONTROLLER_NAME allows data to be sent only when the user calls com.rti.dds.publication.FlowController.trigger_flow. With each trigger, all accumulated data since the previous trigger is sent (across all com.rti.dds.publication.Publisher or com.rti.dds.publication.DataWriter instances). In other words, the network traffic shape is fully controlled by the user. Any accumulated samples destined for the same destination are coalesced into as few network packets as possible.
This external trigger source is ideal for users who want to implement some form of closed-loop flow control or who want to only put data on the wire every so many samples (e.g. with the number of samples based on Transport.Property_t.gather_send_buffer_count_max).
Essentially, this is equivalent to a user-created com.rti.dds.publication.FlowController with the following com.rti.dds.publication.FlowControllerProperty_t settings:
- com.rti.dds.publication.FlowControllerProperty_t.scheduling_policy = FlowControllerSchedulingPolicy.EDF_FLOW_CONTROLLER_SCHED_POLICY
- com.rti.dds.publication.FlowControllerProperty_t.token_bucket max_tokens = ResourceLimitsQosPolicy.LENGTH_UNLIMITED
- com.rti.dds.publication.FlowControllerProperty_t.token_bucket tokens_added_per_period = ResourceLimitsQosPolicy.LENGTH_UNLIMITED
- com.rti.dds.publication.FlowControllerProperty_t.token_bucket tokens_leaked_per_period = ResourceLimitsQosPolicy.LENGTH_UNLIMITED
- com.rti.dds.publication.FlowControllerProperty_t.token_bucket period = com.rti.dds.infrastructure.Duration_t.INFINITE
- com.rti.dds.publication.FlowControllerProperty_t.token_bucket bytes_per_token = ResourceLimitsQosPolicy.LENGTH_UNLIMITED
RTI Connext Java API Version 4.5f
Copyright © 17 Mar 2012
Real-Time Innovations, Inc