HP Reliable Transaction Router Getting Started page 76

Reliable transaction router
Table of Contents

Advertisement

Application Programming Interfaces
Example of an open channel call in an RTR client program:
Sample C client
code
status = rtr_open_channel(&Channel,
if (Status != RTR_STS_OK)
Example of a receive message call in an RTR server program:
Sample C server
code
status = rtr_receive_message(&Channel,
if (status != RTR_STS_OK)
A client can have one or multiple channels, and a server can
have one or multiple channels. A server can use concurrent
servers, each with one channel. How you create your design
depends on whether you have a single CPU or a multiple CPU
machine, and on your overall design goals and implementation
requirements. For a more complete discussion of application
designs, refer to the HP Reliable Transaction Router Application
Design Guide.
4–22 RTR Interfaces
Flags,
Facility,
Recipient,
RTR_NO_PEVTNUM,
Access,
RTR_NO_NUMSEG,
RTR_NO_PKEYSEG);
RTR_NO_FLAGS,
RTR_ANYCHAN,
MsgBuffer,
DataLen,
RTR_NO_TIMOUTMS,
&MsgStatusBlock);

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Reliable Transaction Router and is the answer not in the manual?

This manual is also suitable for:

Aa-rle1c-te

Table of Contents