Condition | A Condition can be added to a WaitSet to provide synchronous event notification |
ContentFilteredTopic | ContentFilteredTopic provides a topic that may include data filtered from a related Topic. The ContentFilteredTopic is associated with another un-filtered topic related_topic. It applies a filter to the data of the related topic. If a data sample passes the filter, it will be made available to a DataReader associated with the ContentFilteredTopic |
DataReader | The DataReader entity allows the application to subscribe to and read data |
DataReaderListener | The DataReaderListener provides asynchronous notification of DataReader events |
DataReaderQos | Structure that holds DataReader Quality of Service policies |
DataWriter | The DataWriter entity provides an interface for the application to publish (write) data. The DataWriter is an abstract class that is extended to support a particular data type required by the application. A DataReader is associated with, and writes on, a single Topic |
DataWriterListener | The DataWriterListener provides asynchronous notification of DataWriter events |
DataWriterQos | Structure that holds DataWriter Quality of Service policies |
DDS | The 'DDS' class includes several convient constants |
DDS_MultiTopic | DDS_MultiTopic provides a topic that may include data from multiple Topics |
DeadlineQosPolicy | This QoS policy establishes a minimum update period for data instances |
DestinationOrderQosPolicy | This QoS policy controls how each Subscriber orders received data samples |
DomainEntity | Base class for all DDS Domain Entities |
DomainParticipant | The DomainParticipant is used to configure, create and destroy Publisher, Subscriber and Topic objects |
DomainParticipantFactory | DomainParticipantFactory constructs DomainParticipants. The |
DomainParticipantFactoryQos | Structure that holds DomainParticipantFactory Quality of Service policies |
DomainParticipantListener | The DomainParticipantListener provides asynchronous notification of DomainParticipant events |
DomainParticipantQos | Structure that holds DomainParticipant Quality of Service policies |
DurabilityQosPolicy | |
DurabilityServiceQosPolicy | |
Duration_t | Duration_t is used to indicate a duration of time |
Entity | Base class for all DDS Entities |
EntityFactoryQosPolicy | |
GroupDataQosPolicy | Allows the application to attach arbitrary information to a Publisher or Subscriber |
GuardCondition | A GuardCondition is a Condition where the trigger_value is under application control |
HistoryQosPolicy | Controls the ammount of historical data maintained by a DataReader or DataWriter |
InconsistentTopicStatus | Status related to the on_inconsistent_topic listener methods of the TopicListener structure |
LatencyBudgetQosPolicy | Specifies allowable latency |
LifespanQosPolicy | Specifies the maximum duration of validity of the data written by the DataWriter |
LivelinessChangedStatus | Status related to the on_liveliness_changed listener methods of the DataReader, Subscriber, and DomainParticipant structures |
LivelinessLostStatus | Status related to the on_liveliness_lost listener methods of the DataWriter, Publisher, and DomainParticipant structures |
LivelinessQosPolicy | Determines the mechanism and parameters used by the application to determine whether an Entity is alive |
OfferedDeadlineMissedStatus | Status related to the on_offered_deadline_missed listener methods of the DataWriter, Publisher, and DomainParticipant structures |
OfferedIncompatibleQosStatus | Status related to the on_offered_incompatible_qos listener methods of the DataWriter, Publisher, and DomainParticipant structures |
OwnershipQosPolicy | Determines instance ownership in the case of multple writers. CoreDX DDS supports both SHARED_OWNERSHIP_QOS and EXCLUSIVE_OWNERSHIP_QOS |
OwnershipStrengthQosPolicy | Defines the strength, or priority, of a Writer. The strength is used to determine ownership in the case of EXCLUSIVE_OWNERSHIP_QOS. When multiple writers publish data about the same instance, the stronger writer is considered the owner, and data from other writers is not delivered to the reader |
PartitionQosPolicy | |
PresentationQosPolicy | Controls the presentation of received data samples to the application. CoreDX DDS currently supports only the access_scope = INSTANCE_PRESENTATION_QOS policy |
PublicationMatchedStatus | Status related to the on_publication_matched listener methods of the DataWriter, Publisher, and DomainParticipant structures |
Publisher | The Publisher configures, creates, manages and destroys DataWriters |
PublisherListener | The PublisherListener provides asynchronous notification of Publisher events |
PublisherQos | Structure that holds Publisher Quality of Service policies |
QueryCondition | The trigger_value is driven by the data available, after applying the filter, in the associated DataReader |
ReadCondition | A ReadCondition is a specialized Condition associated with a DataReader |
ReaderDataLifecycleQosPolicy | Specifies the lifecycle behavior of data instances managed by the DataReader |
ReliabilityQosPolicy | Indicates the level of reliability offered/provided by the Entity. If kind is RELIABLE_RELIABILITY_QOS, then the middleware will attempt to deliver all samples in the history cache. If samples are not received, then they will be retried |
RequestedDeadlineMissedStatus | Status related to the on_requested_deadline_missed listener methods of the DataReader, Subscriber, and DomainParticipant structures |
RequestedIncompatibleQosStatus | Status related to the on_requested_incompatible_qos listener methods of the DataReader, Subscriber, and DomainParticipant structures |
ResourceLimitsQosPolicy | Specifies the resources that the Service can use to maintain data samples and instances |
RTPSReaderQosPolicy | |
RTPSWriterQosPolicy | |
SampleInfo | The SampleInfo structure contains information associated with each Sample. The DataReader.read() and take() operations return two vectors. One vector contains Sample(s) and the other contains SampleInfo(s). There is a one-to-one correspondence between items in these two vectors. Each Sample is described by the corresponding SampleInfo instance |
SampleLostStatus | Status related to the on_sample_lost listener methods of the DataReader, Subscriber, and DomainParticipant structures |
SampleRejectedStatus | Status related to the on_sample_rejected listener methods of the DataReader, Subscriber, and DomainParticipant structures |
StatusCondition | A StatusCondition is a condition associated with an Entity. The trigger_value is driven by the communication status of the associated Entity |
Subscriber | The Subscriber configures, creates, manages and destroys DataReaders |
SubscriberListener | The SubscriberListener provides asynchronous notification of Subscriber events |
SubscriberQos | Structure that holds DDS_Subscriber Quality of Service policies |
SubscriptionMatchedStatus | Status related to the on_subscription_matched listener methods of the DataReader, Subscriber, and DomainParticipant structures |
Time_t | Time_t is used to specify an point in time |
TimeBasedFilterQosPolicy | Defines a filter based on time between samples. The DataReader indicates that it wants at most one sample for each instance every minimum_separation interval |
Topic | Topic is the basic description of data to be published or subscribed. A topic is identified by a name and a type. A Topic is created by calling DomainParticipant.create_topic(). Prior to creating a Topic, the associated data type must be registered with the DomainParticipant via a call to the TypeSupportXYZ.register_type() function. [The register_type() function is auto-generated 'type-specific' code.] |
TopicDataQosPolicy | Allows the application to attach arbitrary information to a Topic QoS |
TopicDescription | TopicDescription is an interface that provides the foundation for Topic, ContentFilteredTopic, and MultiTopic |
TopicListener | The TopicListener provides asynchronous notification of Topic events |
TopicQos | Structure that holds DDS_Topic Quality of Service policies |
TransportPriorityQosPolicy | A hint to the middleware to help configure the transport priority mechanism |
UserDataQosPolicy | Allows the application to attach arbitrary information to a DomainParticipant, DataWriter or DataReader |
WaitSet | A DDS_WaitSet maintains a set of Condition objects and allows the application to wait until one or more of them have a trigger_value of TRUE |
WriterDataLifecycleQosPolicy | Specifies the lifecycle behavior of data instances managed by the DataWriter. If autodispose_unregistered_instances is true, then the DataWriter will automatically dispose any instances that are unregistered. Note: When a DataWriter is deleted, it will automatically unregister all of its instances. With this policy == true, then all instances will also be disposed |