-&term(Listen socket) A &ital(TCP) socket used to await incoming connection requests. Listen sockets are defined
- by an interface and port number combination where the port number is unique for the interface.
-
-&term(Message) A series of bytes transmitted from the application to another RMR based application. A message
- is comprised of RMR specific data (a header), and application data (a payload).
-
-&term(Message buffer) A data structure used to describe a message which is to be sent or has been received.
- The message buffer includes the payload length, message type, message source, and other information.
-
-&term(Messgae type) A signed integer (0-32000) which identifies the type of message being transmitted, and is
- one of the two components of a &ital(routing key.) See &ital(Subscription ID.)
-
-&term(Payload) The portion of a message which holds the user data to be transmitted to the remote &ital(endpoint.)
- The payload contents are completely application defined.
-
-&term(RMR context) A set of information which defines the current state of the underlying transport connections that
- RMR is managing. The application will be give a context reference (pointer) that is supplied to most
- RMR functions as the first parameter.
-
-&term(Round robin) The method of selecting an &ital(endpoint) from a list such that all &ital(endpoints) are selected
- before starting at the head of the list.
-
-&term(Route table) A series of "rules" which define the possible &ital(endpoints) for each &ital(message key.)
-
-&term(Route table manager) An application responsible for building a &ital(route table) and then distributing it to
+&term(Listen socket) A &ital(TCP) socket used to await incoming
+ connection requests. Listen sockets are
+ defined by an interface and port number
+ combination where the port number is unique
+ for the interface.
+
+&term(Message) A series of bytes transmitted from the application to
+ another RMR based application. A message is
+ comprised of RMR specific data (a header), and
+ application data (a payload).
+
+&term(Message buffer) A data structure used to describe a message
+ which is to be sent or has been received. The
+ message buffer includes the payload length,
+ message type, message source, and other
+ information.
+
+&term(Messgae type) A signed integer (0-32000) which identifies the
+ type of message being transmitted, and is one
+ of the two components of a &ital(routing key.)
+ See &ital(Subscription ID.)
+
+&term(Payload) The portion of a message which holds the user data to
+ be transmitted to the remote &ital(endpoint.)
+ The payload contents are completely
+ application defined.
+
+&term(RMR context) A set of information which defines the current
+ state of the underlying transport connections
+ that RMR is managing. The application will be
+ give a context reference (pointer) that is
+ supplied to most RMR functions as the first
+ parameter.
+
+&term(Round robin) The method of selecting an &ital(endpoint) from a
+ list such that all &ital(endpoints) are
+ selected before starting at the head of the list.
+
+&term(Route table) A series of "rules" which define the possible
+ &ital(endpoints) for each &ital(message key.)
+
+&term(Route table manager) An application responsible for building a
+ &ital(route table) and then distributing it to