RTI Connext C API Version 7.5.0
Request-Reply Examples

Examples on how to use the request-reply API .

Examples on how to use the request-reply API .

Request-Reply code examples.

Request-Reply Examples

Requesters and Repliers provide a way to use the Request-Reply communication pattern on top of the DDS entities. An application uses a Requester to send requests to a Replier; another application using a Replier receives a request and can send one or more replies for that request. The Requester that sent the request (and only that one) will receive the reply (or replies).

DDS Types

RTI Connext uses DDS data types for sending and receiving requests and replies. Valid types are those generated by the rtiddsgen code generator, the DDS built-in types, and DynamicData. Refer to the Core Libraries User's Manual and the following links for more information:

Set up

Requester: sending requests and receiving replies

Replier: receiving requests and sending replies

Note
To use Request-Reply you need to build and link your application with the additional rticonnextmsgc library.

The examples in this section require the following header files:

#include "connext_c/connext_c_requester.h"
#include "connext_c/connext_c_replier.h"
#include "connext_c/connext_c_simple_replier.h"

Creating a Requester

Creating a Requester with optional parameters

See also
Creating a Requester
Configuring Request-Reply QoS profiles

Requester example

Taking loaned samples

See also
Requester example
Replier example

Correlating requests and replies

See also
Requester example
Replier example

Creating a Replier

Replier example

See also
Requester example

SimpleReplier example

See also
Requester example

Configuring Request-Reply QoS profiles

If you do not specify your own quality of service parameters (in RTI_Connext_RequesterParams and RTI_Connext_ReplierParams), a FooBarRequester and FooBarReplier are created using a default configuration defined in the built-in profile DDS_PROFILE_PATTERN_RPC. You use this built-in profile as the base for your own profiles:

<?xml version="1.0"?>
<dds xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://community.rti.com/schema/current/rti_dds_profiles.xsd">
<qos_library name="RequestReplyExampleProfiles">
<!-- Use these profiles to customize the Requester or Replier QoS -->
<!-- These profiles inherit from the built-in profile
BuiltinQosLib::Pattern.RPC, which defines the default values for
the DataWriters and DataReaders created by a Requester or Replier
-->
<qos_profile name="RequesterExampleProfile" base_name="BuiltinQosLib::Pattern.RPC">
<!-- Set the QoS for the DataReader created by the Requester -->
<!--
<datareader_qos>
...
</datareader_qos>
-->
<!-- Set the QoS for the DataWriter created by the Requester -->
<!--
<datawriter_qos>
...
</datawriter_qos>
-->
</qos_profile>
<qos_profile name="ReplierExampleProfile" base_name="BuiltinQosLib::Pattern.RPC">
<!-- Set the QoS for the DataReader created by the Replier -->
<!--
<datareader_qos>
...
</datareader_qos>
-->
<!-- Set the QoS for the DataWriter created by the Replier -->
<!--
<datawriter_qos>
...
</datawriter_qos>
-->
</qos_profile>
</qos_library>
</dds>

The example Creating a Requester with optional parameters shows how to create a FooBarRequester using this profile.

See also
Creating a Requester with optional parameters
Configuring QoS Profiles with XML