Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
.ix pause
&h1(Appendix &gloss_appendix -- Glossary)
Many terms in networking can be interpreted with multiple meanings,
.ix pause
&h1(Appendix &gloss_appendix -- Glossary)
Many terms in networking can be interpreted with multiple meanings,
-and several terms used in this document are RMR specific. The
-following definitions are the meanings of terms used within this
-document and should help the reader to understand the intent of
+and several terms used in various RMR documentation are RMR specific.
+The following definitions are the meanings of terms used within RMR
+documentation and should help the reader to understand the intent of
-&beg_dlist( &1.0i Helvetica-bold )
-&term(application) A programme which uses RMR to send and/or receive
+&beg_dlist( &1.0i Helvetica-bold : : 25,70 )
+&ditem(application) A programme which uses RMR to send and/or receive
prevent further successful processing by
RMR. Critical errors usually indicate that the
application should abort.
prevent further successful processing by
RMR. Critical errors usually indicate that the
application should abort.
to the application, but which is available to
the application (and referenced libraries)
through the &cw(getenv) system
to the application, but which is available to
the application (and referenced libraries)
through the &cw(getenv) system
not affect the overall processing by RMR, but
may impact certain aspects such as the ability
to communicate with a specific endpoint.
Errors generally indicate that something,
usually external to RMR, must be addressed.
not affect the overall processing by RMR, but
may impact certain aspects such as the ability
to communicate with a specific endpoint.
Errors generally indicate that something,
usually external to RMR, must be addressed.
&cw(gethostbyname) system call. In a
containerised environment this might be the
container or service name depending on how the
&cw(gethostbyname) system call. In a
containerised environment this might be the
container or service name depending on how the
connection requests. Listen sockets are
defined by an interface and port number
combination where the port number is unique
for the interface.
connection requests. Listen sockets are
defined by an interface and port number
combination where the port number is unique
for the interface.
another RMR based application. A message is
comprised of RMR specific data (a header), and
application data (a payload).
another RMR based application. A message is
comprised of RMR specific data (a header), and
application data (a payload).
which is to be sent or has been received. The
message buffer includes the payload length,
message type, message source, and other
information.
which is to be sent or has been received. The
message buffer includes the payload length,
message type, message source, and other
information.
type of message being transmitted, and is one
of the two components of a &ital(routing key.)
See &ital(Subscription ID.)
type of message being transmitted, and is one
of the two components of a &ital(routing key.)
See &ital(Subscription ID.)
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.
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(Route table) A series of "rules" which define the possible
- &ital(endpoints) for each &ital(message key.)
+&ditem(Route table) A series of "rules" which define the possible
+ &ital(endpoints) for each &ital(routing key.)
-&term(Routing) The process of selecting an &ital(endpoint) which will
-be the recipient of a message.
+&ditem(Routing) The process of selecting an &ital(endpoint) which will
+ be the recipient of a message.
identifies the subscription characteristic of
a message. It is used in conjunction with the
&ital(message type) to determine the
&ital(routing key.)
identifies the subscription characteristic of
a message. It is used in conjunction with the
&ital(message type) to determine the
&ital(routing key.)
internet protocol which provides for lossless
packet transportation, usually over IP.
internet protocol which provides for lossless
packet transportation, usually over IP.
is a lightweight process which executes in
concurrently with the application and shares
the same address space. RMR uses threads to
manage asynchronous functions such as route
table updates.
is a lightweight process which executes in
concurrently with the application and shares
the same address space. RMR uses threads to
manage asynchronous functions such as route
table updates.
that the application may populate with data
that allows for tracing the progress of the
transaction or application activity across
components. RMR makes no use of this data.
that the application may populate with data
that allows for tracing the progress of the
transaction or application activity across
components. RMR makes no use of this data.
buffer) which the application may populate
with information related to the
transaction. RMR makes use of the transaction
buffer) which the application may populate
with information related to the
transaction. RMR makes use of the transaction
lived and that the operation, if retried by
the application, might be successful. C
programmers will recognise this as
&cw(EAGAIN.)
lived and that the operation, if retried by
the application, might be successful. C
programmers will recognise this as
&cw(EAGAIN.)