branch
A subdivision of a bank; perhaps in another town.
broadcast
A nontransactional message.
callout server
A server process used for transactional authentication.
channel
A logical port opened by an application with an identifier to exchange messages with RTR.
client
A client is always a client application, one that initiates and demarcates a piece of work. In the context of RTR, a client must run on a node defined to have the frontend role. Clients typically deal with presentation services, handling forms input, screens, and so on. A browser, perhaps running an applet, could connect to a web application that acts as an RTR client, sending data to a server through RTR.
In other contexts, a client can be a physical system, but in the context of RTR and in this document, such a system is always called a frontend or a node.
client classes
C++ foundation classes used for implementing client applications.
commit process
The transactional process by which a transaction is prepared, accepted, committed, and hardened in the database.
commit sequence number (CSN)
A sequence number assigned to an RTR commit group, established by the vote window, the time interval during which transaction response is returned from the backend to the router. All transactions in the commit group have the same CSN and lock the database.
