RTR Facilities Bridge the Gap
RTR Facilities Bridge the Gap
Many applications can use RTR at the same time without interfering with one another. This is achieved by defining a separate facility for each application.
When an application calls the rtr_open_channel( ) routine to declare a channel as a client or server, it specifies the name of the facility it will use.
See the RTR System Manager's Manual for information on how to define facilities.
Broadcasts
Sometimes an application has a requirement to send unsolicited messages to multiple recipients.
An example of such an application is a commodity trading system, where the clients submit orders and also need to be informed of the latest price changes.
The RTR broadcast capability meets this requirement.
Recipients subscribe to a class of broadcasts; a sender broadcasts a message in this class, all interested recipients receive the message.
RTR permits clients to broadcast messages to one or more servers, or servers to broadcast to one or more clients. If a server needs to broadcast a message to another server, it must open a second channel as a client.
Flexibility and Growth
RTR allows you to cope easily with changes in:
•Network demand
Architectural Concepts