ContentFilteredTopic is an implementation of ITopicDescription that allows for content-based subscriptions. ContentFilteredTopic describes a more sophisticated subscription that indicates the subscriber does not want to necessarily see all values of each instance published under the Topic. Rather, it wants to see only the values whose contents satisfy certain criteria. This class therefore can be used to request content-based subscriptions.
A DataReader allows the application to declare the data it wishes to receive (i.e., make a subscription) and to access the data received by the attached Subscriber.
Holds the DataReader Quality of Service policies.
DataWriter allows the application to set the value of the data to be published under a given Topic.
Holds the DataWriter Quality of Service policies.
This policy is useful for cases where a Topic is expected to have each instance updated periodically. On the publishing side this setting establishes a contract that the application must meet. On the subscribing side the setting establishes a minimum requirement for the remote publishers that are expected to supply the data values.
The DomainParticipant represents the participation of the application on a communication plane that isolates applications running on the same set of physical computers from each other.
A domain establishes a virtual network linking all applications that share the same DomainId and isolating them from applications running on different domains. In this way, several independent distributed applications can coexist in the same physical network without interfering, or even being aware of each other.
Allows the creation and destruction of DomainParticipant objects.
Holds the DomainParticipantFactory Quality of Service policies.
Holds the DomainParticipant Quality of Service policies.
This policy controls the behavior of the Entity as a factory for other entities.
This policy controls the behavior of DDS when the value of an instance changes before it is finally communicated to some of its existing DataReader entities.
This policy provides a means for the application to indicate to the middleware the “urgency” of the data-communication. By having a non-zero duration DDS can optimize its internal operation. This policy is considered a hint. There is no specified mechanism as to how the service should take advantage of this hint.
The purpose of this QoS is to avoid delivering "stale" data to the application.
Each data sample written by the DataWriter has an associated 'expiration time' beyond which the data should not be delivered to any application. Once the sample expires, the data will be removed from the DataReader caches as well as from the transient and persistent information caches.
This policy controls the mechanism and parameters used by DDS to ensure that particular entities on the network are still "alive".
MultiTopic is an implementation of ITopicDescription that allows subscriptions to combine/filter/rearrange data coming from several topics. MultiTopic allows a more sophisticated subscription that can select and combine data received from multiple topics into a single resulting type(specified by the inherited type name). The data will then be filtered(selection) and possibly re-arranged (aggregation/projection) according to a subscription expression with the expression parameters.
This policy controls whether DDS allows multiple DataWriter objects to update the same instance (identified by Topic + key) of a data-object.
This QoS policy should be used in combination with the Ownership policy. It only applies to the situation case where ownership kind is set to Exclusive.
This policy allows the introduction of a logical partition concept inside the 'physical' partition induced by a domain.
The Presentation QoS policy controls how changes to instances by publishers are presented to data readers. It affects the relative ordering of these changes and the scope of this ordering. Additionally, this policy introduces the concept of coherent change sets.
A Publisher is the object responsible for the actual dissemination of publications.
Abstract class that can be implemented by an application-provided class and then registered with the Publisher such that the application can be notified of relevant status changes.
Holds the Publisher Quality of Service policies.
Hold a counter for the QoS policies
QueryCondition objects are specialized ReadCondition objects that allow the application to also specify a filter on the locally available data.
ReadCondition objects are conditions specifically dedicated to read operations and attached to one DataReader
This policy controls the behavior of the DataReader with regards to the lifecycle of the data-instances it manages, that is, the data-instances that have been received and for which the DataReader maintains some internal resources.
This policy controls the resources that DDS can use in order to meet the requirements imposed by the application and other QoS settings.
Information that accompanies each sample that is read or taken.
A Subscriber is the object responsible for the actual reception of the data resulting from its subscriptions.
Abstract class that can be implemented by an application-provided class and then registered with the Subscriber such that the application can be notified of relevant status changes.
Holds the Subscriber Quality of Service policies.
Topic is the most basic description of the data to be published and subscribed. A Topic is identified by its name, which must be unique in the whole Domain. In addition (by virtue of implemeting ITopicDescription) it fully specifies the type of the data that can be communicated when publishing or subscribing to the Topic. Topic is the only ITopicDescription that can be used for publications and therefore associated to a DataWriter.
The purpose of this QoS is to allow the application to attach additional information to the created Topic such that when a remote application discovers their existence it can examine the information and use it in an application-defined way.
Abstract class that can be implemented by an application-provided class and then registered with the Topic such that the application can be notified of relevant status changes.
Holds the Topic Quality of Service policies.
The purpose of this QoS is to allow the application to take advantage of transports capable of sending messages with different priorities.
The purpose of this QoS is to allow the application to attach additional information to the created Entity objects such that when a remote application discovers their existence it can access that information and use it for its own purposes.
Global unique identifier of the built-in topics.
Structure for duration representation
The InconsistentTopic status indicates that a topic was attempted to be registered that already exists with different characteristics. Typically, the existing topic may have a different type associated with it.
Type definition for an instance handle.
Indicates if the samples are from a live DataWriter or not.
Represent a bit-mask of InstanceStateKind
The LivelinessChanged status indicates that there have been liveliness changes for one or more data writers that are publishing instances for this data reader.
The LivelinessLost status indicates that the liveliness that the data writer committed through its Liveliness QoS has not been respected. This means that any connected data readers will consider this DataWriter no longer active.
The OfferedDeadlineMissed status indicates that the deadline offered by the DataWriter has been missed for one or more instances.
The OfferedIncompatibleQos status indicates that an offered QoS was incompatible with the requested QoS of a DataReader.
Class that contains information about available DomainParticipants within the system.
Class that contains information about available DataWriters within the system.
The RequestedDeadlineMissed status indicates that the deadline requested via the DeadlineQosPolicy was not respected for a specific instance.
The RequestedIncompatibleQos status indicates that one or more QoS policy values that were requested were incompatible with what was offered.
The SampleLost status indicates that a sample has been lost and never received by the DataReader.
The SampleRejected status indicates that a sample received by the data reader has been rejected.
Indicates whether or not a sample has ever been read.
Represent a bit-mask of SampleStateKind
Kinds of communication status.
Represent a bit-mask of StatusKind
Class that contains information about available DataReaders within the system.
The SubscriptionMatched status indicates that either a compatible DataWriter has been matched or a previously matched data writer has ceased to be matched.
Structure for timestamp representation
Class that contains information about available Topics within the system.
Indicates whether or not an instance is new.
Represent a bit-mask of ViewStateKind
This enumeration defines the valid kinds of the DestinationOrderQosPolicy Kind.
This enumeration defines the valid kinds of the DurabilityQosPolicy Kind.
This enumeration defines the valid kinds of the HistoryQosPolicy Kind.
This enumeration defines the valid kinds of the LivelinessQosPolicy Kind.
This enumeration defines the valid kinds of the OwnershipQosPolicy Kind.
This enumeration defines the valid kinds of the PresentationQosPolicy AccessScope.
This enumeration defines the valid kinds of the ReliabilityQosPolicy Kind.
Represents the various return code values that DDS operations return.
This enumeration defines the valid values of the SampleRejectedStatus LastReason.