RTI Connext C API  Version 6.1.2

Contains the parameters for creating a FooBarRequester. More...

Data Fields

DDS_DomainParticipantparticipant
 The participant this requester uses to join a DDS domain. More...
 
char * service_name
 The service name that Repliers and Requester use to match and communicate. More...
 
char * request_topic_name
 Sets a specific request topic name. More...
 
char * reply_topic_name
 Sets a specific reply topic name. More...
 
char * qos_library_name
 Sets the library that contains the RTI_Connext_RequesterParams::qos_profile_name. More...
 
char * qos_profile_name
 Sets a QoS profile for the entities in this requester. More...
 
const struct DDS_DataWriterQosdatawriter_qos
 Sets the quality of service of the request DataWriter. More...
 
const struct DDS_DataReaderQosdatareader_qos
 Sets the quality of service of the request DataReader. More...
 
DDS_Publisherpublisher
 Sets a specific Publisher. More...
 
DDS_Subscribersubscriber
 Sets a specific Subscriber. More...
 

Detailed Description

Contains the parameters for creating a FooBarRequester.

The following parameters are required to create a Requester:

The rest of the parameters that can be set in a RequesterParams object are optional.

See also
Creating a Requester with optional parameters

Field Documentation

◆ participant

DDS_DomainParticipant* RTI_Connext_RequesterParams::participant

The participant this requester uses to join a DDS domain.

◆ service_name

char* RTI_Connext_RequesterParams::service_name

The service name that Repliers and Requester use to match and communicate.

A Requester and a Replier need to be configured with the same topic names in order to match.

The service name is used to generate a request topic and a reply topic that the Requester and Replier will use to communicate. For example, the service name "MyService" will be used to create topics named "MyServiceRequest" and "MyServiceReply".

In some cases, the name of these topics is known beforehand or needs to be customized for another reason. The service name can be overridden by setting specific request and reply topic names using RTI_Connext_RequesterParams::request_topic_name and RTI_Connext_RequesterParams::reply_topic_name.

◆ request_topic_name

char* RTI_Connext_RequesterParams::request_topic_name

Sets a specific request topic name.

The specified topic name will be used, instead of allowing a topic name to be generated based on the RTI_Connext_RequesterParams::service_name. If that topic already exists, it will be reused.

◆ reply_topic_name

char* RTI_Connext_RequesterParams::reply_topic_name

Sets a specific reply topic name.

The specified topic name will be used, instead of allowing a topic name to be generated based on the RTI_Connext_RequesterParams::service_name. If that topic already exists, it will be reused.

◆ qos_library_name

char* RTI_Connext_RequesterParams::qos_library_name

◆ qos_profile_name

char* RTI_Connext_RequesterParams::qos_profile_name

Sets a QoS profile for the entities in this requester.

Specifies an XML QoS profile that will be used to configure the quality of service of a Requester's underlying request DataWriter and reply DataReader.

Within that profile, the DataWriter QoS in <datawriter_qos> will be used to configure the request DataWriter and the DataReader.

Alternatively, you can set the QoS using the DataWriterQos and DataReaderQos objects (RTI_Connext_RequesterParams::datawriter_qos, RTI_Connext_RequesterParams::datareader_qos).

The library where this profile is located has to be set with RTI_Connext_RequesterParams::qos_library_name

See also
RTI_Connext_RequesterParams::qos_library_name
Configuring Request-Reply QoS profiles
Configuring QoS Profiles with XML

◆ datawriter_qos

const struct DDS_DataWriterQos* RTI_Connext_RequesterParams::datawriter_qos

Sets the quality of service of the request DataWriter.

See also
RTI_Connext_RequesterParams::qos_profile_name

◆ datareader_qos

const struct DDS_DataReaderQos* RTI_Connext_RequesterParams::datareader_qos

Sets the quality of service of the request DataReader.

See also
RTI_Connext_RequesterParams::qos_profile_name

◆ publisher

DDS_Publisher* RTI_Connext_RequesterParams::publisher

Sets a specific Publisher.

By default, a Requester uses the DomainParticipant's implicit Publisher. Sometimes a different Publisher may be needed, for example, to use non-default PublisherQos.

◆ subscriber

DDS_Subscriber* RTI_Connext_RequesterParams::subscriber

Sets a specific Subscriber.

By default, a Requester uses the DomainParticipant's implicit Subscriber. Sometimes a different Subscriber may be needed, for example, to use non-default SubscriberQos.