Domain Module

Contains the DDS_DomainParticipant class that acts as an entrypoint of RTI Connext DDS Micro and acts as a factory for many of the classes. The DDS_DomainParticipant also acts as a container for the other objects that make up RTI Connext DDS Micro. Testing RTI Connext DDS Micro Secure command. More...

Modules
	DomainParticipantFactory
	DDS_DomainParticipantFactory entity and associated elements
	DomainParticipant
	DDS_DomainParticipant entity and associated elements
	Discovery
	Descriptions of remote entities used for discovery.

Macros
#define	DDS_TheParticipantFactory   DDS_DomainParticipantFactory_get_instance()
	Can be used as an alias for the singleton factory returned by the operation DDS_DomainParticipantFactory_get_instance().

Typedefs
typedef DDS_DOMAINID_TYPE_NATIVE	DDS_DomainId_t
	<<cert>> An integer that indicates in which domain a DDS_DomainParticipant communicates.

---

Detailed Description

Contains the DDS_DomainParticipant class that acts as an entrypoint of RTI Connext DDS Micro and acts as a factory for many of the classes. The DDS_DomainParticipant also acts as a container for the other objects that make up RTI Connext DDS Micro. Testing RTI Connext DDS Micro Secure command.

Defines the DDS domain package.

This image describes the DDS Domain Package, as described by the DDS standard. Note that not all functions and objects shown in this diagram are supported by RTI Connext DDS Micro. Please read the information on the individual types to determine whether a function is supported.

---

Macro Definition Documentation

#define DDS_TheParticipantFactory   DDS_DomainParticipantFactory_get_instance()

Can be used as an alias for the singleton factory returned by the operation DDS_DomainParticipantFactory_get_instance().

See also:

DDS_DomainParticipantFactory_get_instance

---

Typedef Documentation

typedef DDS_DOMAINID_TYPE_NATIVE DDS_DomainId_t

<<cert>> An integer that indicates in which domain a DDS_DomainParticipant communicates.

Participants with the same DDS_DomainId_t are said to be in the same domain, and can thus communicate with one another.

The lower limit for a domain ID is 0. The upper limit for a domain ID is determined by the guidelines of the RTPS specification of the well-known ports on which a Participant will listen for discovery metatraffic from other Participants.