=====================================================
RTI Connext Messaging
Request-Reply Example Application
=====================================================

Welcome to Connext.


Compiling this Example
----------------------

Before compiling make sure that the environment variable NDDSHOME is defined 
and that it refers to your RTI Connext installation directory. 

To build this example on Windows, open the appropriate solution file for your
version of Microsoft Visual Studio.

To build this example on a UNIX-based system, type the following in a command
shell:

  > make -f make/makefile_RequestReplyPrimes_<architecture>


Running this Example
--------------------
This example is composed of two applications: a requester and a replier.

To run this example on Windows, type the following in two different command
shells, either on the same machine or on different machines:

  > objs\<architecture>\PrimeNumberReplier.exe [<domain_id>]
  > objs\<architecture>\PrimeNumberRequester.exe <n> [<primes_per_reply> [<domain_id>]]

To run this example on a UNIX-based system, type the following in two
different command shells, either on the same machine or on different machines:

  > objs/<architecture>/PrimeNumberReplier [<domain_id>]
  > objs/<architecture>/PrimeNumberRequester <n> [<primes_per_reply> [<domain_id>]]

The Requester and the Replier are configured by the file USER_QOS_PROFILES.xml
located in this directory. You can modify this file to change the example's
behavior.

For more information on using Requesters and Repliers, please consult the
RTI Core Libraries and Utilities Getting Started Guide and User's Manual.

Running a C++11 Requester and a C/C++98/C#/Java Replier
-------------------------------------------------------
C++11 and Python are the only APIs that support enhanced discovery.
This means that a C++11 Requester has to disable the property
`RequesterParams::require_matching_service_on_send_request`
in order to communicate with a C/C++98/C#/Java Replier, and do not call
`wait_for_service()`.
