▼Ncom | |
▼Ntoc | |
▼Ncoredx | |
►NDDS | |
►Nrpc | |
CClientEndpoint | |
CClientParams | |
CListenerBase | |
CReplier | |
CReplierBase | |
CReplierListener | |
CReplierParams | |
CRequester | |
CRequesterListener | |
CRequesterParams | |
CRPCEntity | |
CServiceEndpoint | |
CServiceParams | |
CServiceProxy | |
CServiceStatus | |
CSimpleReplierListener | |
CSimpleRequesterListener | |
CCondition | A Condition can be added to a DDS_WaitSet to provide synchronous event notification |
CConstants | Provides various constants and utility routines used throughout CoreDX DDS |
CContentFilteredTopic | ContentFilteredTopic provides a topic that may include data filtered from a related Topic |
CDataReader | The DataReader entity allows the application to subscribe to and read data |
CDataReaderListener | The DataReaderListener provides asynchronous notification of DataReader events. This listener can be installed during DataReader creation, DomainParticipant_create_yyy(), as well as by calling DataReader_set_listener() |
CDataReaderQos | Structure that holds DataReader Quality of Service policies |
CDataRepresentationQosPolicy | This QoS policy establishes the DataRepresentation (data encoding) offered by a DataWriter or requested by a DataReader |
CDataWriter | 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 |
CDataWriterListener | The DataWriterListener provides asynchronous notification of DataWriter events. This listener can be installed during DataWriter creation, Publisher_create_datawriter(), as well as by calling DataWriter_set_listener() |
CDataWriterQos | Structure that holds DataWriter Quality of Service policies |
CDeadlineQosPolicy | This QoS policy establishes a minimum update period for data instances |
CDestinationOrderQosPolicy | This QoS policy controls how each Subscriber orders received data samples |
CDestinationOrderQosPolicyKind | This enumeration contains the kinds of Destination Ordering |
CDiscoveryQosPolicy | QoS Policy for configuring aspects of the Discovery and Builtin entities |
CDiscoveryQosPolicyDiscoveryKind | This enumeration contains the kinds of Discovery |
CDomainEntity | Base class for all DDS Domain Entities |
CDomainId_t | |
CDomainParticipant | The DomainParticipant is used to configure, create and destroy Publisher, Subscriber and Topic objects |
CDomainParticipantFactory | DomainParticipantFactory constructs DomainParticipants. The |
CDomainParticipantFactoryQos | Structure that holds DomainParticipantFactory Quality of Service policies |
CDomainParticipantListener | |
CDomainParticipantQos | Structure that holds DomainParticipant Quality of Service policies |
CDurabilityQosPolicy | |
CDurabilityQosPolicyKind | This enumeration contains the kinds of Duarbility |
CDurabilityServiceQosPolicy | |
CDuration_t | Represents a time duration with nanosecond resolution |
CEntity | Base class for all DDS Entities |
CEntityFactoryQosPolicy | |
CEntityNameQosPolicy | |
CFooDataReader | The FooDataReader is an example specialized DataReader (generated by the coredx_ddl compiler) for reading data samples of type 'Foo' |
CFooDataWriter | The FooDataWriter is an example specialized DataWriter (generated by the coredx_ddl compiler) for writing data samples of type 'Foo' |
CFooTypeSupport | Impliments the TypeSupport inteface for the Data Type 'Foo' |
CGroupDataQosPolicy | Allows the application to attach arbitrary information to a Publisher or Subscriber |
CGuardCondition | A GuardCondition is a Condition where the trigger_value is under application control |
CHistoryQosPolicy | Controls the ammount of historical data maintained by a DataReader or DataWriter |
CHistoryQosPolicyKind | This enumeration contains the kinds of History |
CInconsistentTopicStatus | InconsistentTopicStatus provides status related to the on_inconsistent_topic listener methods of the TopicListener structure |
CInstanceHandle_t | Used to identify a DDS Entity or data instance. An InstanceHandle is unique within its context. For example, each data instance known by a DataReader is assigned a unique InstanceHandle. However, these handles may not be unique when compared to handles from another DataReader |
CIpTransportInterface | Defines an interface for use by the UdpTransport |
CLatencyBudgetQosPolicy | Specifies allowable latency |
CLifespanQosPolicy | Specifies the maximum duration of validity of the data written by the DataWriter |
CLivelinessChangedStatus | Status related to the on_liveliness_changed listener methods of the DataReader, Subscriber, and DomainParticipant structures |
CLivelinessLostStatus | Status related to the on_liveliness_lost listener methods of the DataWriter, Publisher, and DomainParticipant structures |
CLivelinessQosPolicy | Determines the mechanism and parameters used by the application to determine whether an Entity is alive |
CLivelinessQosPolicyKind | This enumeration contains the kinds of Liveliness |
CLmtTransport | An instance of a LMT Transport that can be added to a DomainParticipant |
CLmtTransportConfig | Structure that holds LMT Transport configuration items |
CLoanedSamples | |
CLocator | Network address |
CLoggingQosPolicy | Controls the amount and kind of data that is logged |
CMultiTopic | MultiTopic provides a topic that may include data from multiple Topics |
COfferedDeadlineMissedStatus | Status related to the on_offered_deadline_missed listener methods of the DataWriter, Publisher, and DomainParticipant structures |
COfferedIncompatibleQosStatus | Status related to the on_offered_incompatible_qos listener methods of the DataWriter, Publisher, and DomainParticipant structures |
COwnershipQosPolicy | Determines instance ownership in the case of multple writers. CoreDX DDS supports both SHARED_OWNERSHIP_QOS and EXCLUSIVE_OWNERSHIP_QOS |
COwnershipQosPolicyKind | This enumeration contains the kinds of Ownership |
COwnershipStrengthQosPolicy | 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 |
CParticipantBuiltinTopicData | The ParticipantBuiltinTopicData is a built-in Data Type that represents Participant Discovery information |
CParticipantBuiltinTopicDataDataReader | The ParticipantBuiltinTopicDataDataReader is a built-in DataReader that can be used to access Participant Discovery information. The reader can be accessed through the special 'builtin' Subscriber via the DomainParticipant.get_builtin_subscriber() routine |
CParticipantLocator | Describes a the location and identity of a potential peer DomainParticipant |
CPartitionQosPolicy | Defines a logical data partition |
CPeerParticipantQosPolicy | Configures a list of DomainParticipant peers to attempt communication with |
CPresentationQosPolicy | Controls the presentation of received data samples to the application. CoreDX DDS currently supports only the access_scope = INSTANCE_PRESENTATION_QOS policy |
CPresentationQosPolicyAccessScopeKind | This enumeration contains the kinds of Access Scope for the PresentationQosPolicy |
CProperty_t | A name-value pair property. The 'propagate' flag indicates if this property should be transfered through discovery |
CPropertyQosPolicy | The PropertyQosPolicy supports adding arbitrary name-value pairs |
CPublicationBuiltinTopicData | The PublicationBuiltinTopicData is a built-in Data Type that represents Publication Discovery information |
CPublicationBuiltinTopicDataDataReader | The PublicationBuiltinTopicDataDataReader is a built-in DataReader that can be used to access Publication Discovery information. The reader can be accessed through the special 'builtin' Subscriber via the DomainParticipant.get_builtin_subscriber() routine |
CPublicationMatchedStatus | Status related to the on_publication_matched listener methods of the DataWriter, Publisher, and DomainParticipant structures |
CPublisher | The Publisher configures, creates, manages and destroys DataWriters |
CPublisherListener | |
CPublisherQos | Structure that holds Publisher Quality of Service policies |
CQosPolicyCount | A QoS Policy identifier, along with a count |
CQosProvider | QosProvider loads QoS settings from a library and provides interfaces to access entity specific QoS Policies |
CQueryCondition | The trigger_value is driven by the data available, after applying the filter, in the associated DataReader |
CReadCondition | A ReadCondition is a specialized Condition associated with a DataReader |
CReaderDataLifecycleQosPolicy | Specifies the lifecycle behavior of data instances managed by the DataReader |
CReliabilityQosPolicy | 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 |
CReliabilityQosPolicyKind | This enumeration contains the kinds of Reliability |
CRequestedDeadlineMissedStatus | Status related to the on_requested_deadline_missed listener methods of the DataReader, Subscriber, and DomainParticipant structures |
CRequestedIncompatibleQosStatus | |
CResourceLimitsQosPolicy | Specifies the resources that the Service can use to maintain data samples and instances |
CRpcQosPolicy | |
CRTPSReaderQosPolicy | QoS Policy for configuring aspects of the RTPS Reader Protocol |
CRTPSWriterQosPolicy | QoS Policy for configuring aspects of the RTPS Writer Protocol |
CSampleInfo | 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 |
CSampleLostStatus | Status related to the on_sample_lost listener methods of the DataReader, Subscriber, and DomainParticipant structures |
CSampleRejectedStatus | Status related to the on_sample_rejected listener methods of the DataReader, Subscriber, and DomainParticipant structures |
►CSslTransport | An instance of a SSL Transport that can be added to a DomainParticipant |
CX509_Der | |
CSslTransportConfig | Structure that holds SSL Transport configuration items |
CStatusCondition | A StatusCondition is a condition associated with an Entity. The trigger_value is driven by the communication status of the associated Entity |
CSubscriber | The Subscriber configures, creates, manages and destroys DataReaders |
CSubscriberListener | The SubscriberListener provides asynchronous notification of Subscriber events. This listener can be installed during Subscriber creation, DomainParticipant_create_subscriber() as well as by calling Subscriber_set_listener() |
CSubscriberQos | Structure that holds DDS_Subscriber Quality of Service policies |
CSubscriptionBuiltinTopicData | The SubscriptionBuiltinTopicData is a built-in Data Type that represents Subscription Discovery information |
CSubscriptionBuiltinTopicDataDataReader | The SubscriptionBuiltinTopicDataDataReader is a built-in DataReader that can be used to access Subscription Discovery information |
CSubscriptionMatchedStatus | Status related to the on_subscription_matched listener methods of the DataReader, Subscriber, and DomainParticipant structures |
CTcpTransport | An instance of a TCP Transport that can be added to a DomainParticipant |
CTcpTransportConfig | Structure that holds TCP Transport configuration items |
CThreadModelQosPolicy | QoS Policy for configuring the threading behavior of the DomainParticipant |
CTime_t | Represents time with nanosecond resolution |
CTimeBasedFilterQosPolicy | 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 |
CTopic | 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.] |
CTopicDataQosPolicy | Allows the application to attach arbitrary information to a Topic QoS |
CTopicDescription | TopicDescription is an abstract that provides the foundation for Topic, ContentFilteredTopic, and MultiTopic |
CTopicListener | The DDS_TopicListener provides asynchronous notification of DDS_Topic events. This listener can be installed during Topic creation (DDS_DomainParticipant_create_topic() and related) as well as by calling DDS_Topic_set_listener() |
CTopicQos | Structure that holds DDS_Topic Quality of Service policies |
CTransport | An instance of a Transport that can be added to a DomainParticipant |
CTransportPriorityQosPolicy | A hint to the middleware to help configure the transport priority mechanism |
CTypeCodeKind | This enumeration contains the kinds of data types used in constructing a Typecode |
CTypecodeQosPolicy | Typecode representing the datatype a DataReader reads or a DataWriter writes |
CTypeConsistencyEnforcementQosPolicy | This QoS policy establishes the policy for establishing consistency of the Reader and Writer data types |
CTypeConsistencyKind | This enumeration contains the kinds of Reliability |
CTypeSupport | |
CUdpTransport | An instance of a Transport that can be added to a DomainParticipant |
CUdpTransportConfig | Structure that holds UDP Transport configuration items |
CUserDataQosPolicy | Allows the application to attach arbitrary information to a DomainParticipant, DataWriter or DataReader |
CWaitSet | 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 |
CWriterDataLifecycleQosPolicy | 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 |