&space
RMr functions do provide for the ability to respond to the specific source
instance of a message allowing for either a request response, or call
-response relationship when needed.
+response relationship when needed.
&h3(The Route Table)
&h3(Environment)
To enable configuration of the library behaviour outside of direct user application
control, RMr supports a number of environment variables which provide information
-to the library.
+to the library.
The following is a list of the various environment variables, what they control
and the defaults which RMr uses if undefined.
value to 0. When set to 1, or missing from the environment, RMR will invoke the
connection interface in the transport mechanism using the non-blocking (asynch)
mode. This will likely result in many "soft failures" (retry) until the connection
- is established, but allows the application to continue unimpeeded should the
+ is established, but allows the application to continue unimpeeded should the
connection be slow to set up.
&di(RMR_BIND_IF) This provides the interface that RMr will bind listen ports to allowing
&di(RMR_SEED_RT) This is used to supply a static route table which can be used for
debugging, testing, or if no route table generator process is being used to
- supply the route table.
+ supply the route table.
If not defined, no static table is used and RMr will not report &ital(ready)
until a table is received.
&end_dlist
rmr_has_str(3),
rmr_tokenise(3),
rmr_mk_ring(3),
+rmr_realloc_payload(3),
rmr_ring_free(3),
rmr_set_trace(3),
rmr_torcv_msg(3),