Overview

The functionality of RTserver and RTclient is layered on top of connections and messages, but adds greater functionality and ease of use. Some of these functions are:

RTserver and RTclient have simplified setup and control through options, which require no programming

RTserver can partition a group of RTclients into a project

RTserver and RTclient use logical addresses called subjects for the sender property and destination property of messages, which enable powerful yet simple publish-subscribe services

Subjects are arranged in a hierarchical namespace with wildcard capabilities, which makes it easier to build large projects

A group of RTservers can distribute the load of publish-subscribe message routing with dynamic message routing that offers greater scalability and flexibility

An RTclient can automatically start an RTserver, automatically restart an RTserver, and even continue running when an RTserver is temporarily unavailable

RTserver and RTclient have advanced guaranteed message delivery (GMD) capabilities, such as automatic recovery from most network failures

Much information about RTservers and RTclients can be monitored, which allows you to easily debug, examine, and control your projects

Load balancing can be used to publish messages to one subscriber instead of all

The RTclient API can be used safely in multi-threaded programs

This chapter describes the C++ interface to RTserver and how to work with the RTclient C++ API.

This chapter should be considered a companion to the TIBCO SmartSockets User’s Guide. You may wish to read the detailed information on RTserver and RTclient processes in the TIBCO SmartSockets User’s Guide before proceeding further in this chapter. The intent of this chapter is to focus on creating RTclient processes using the C++ class library.