...
The following are announcements related to RMR during the past 30 days; newest announcements first.
2019 September 18:
- Version 1.7.0: Connection mode changed to be non-blocking by default. Set the environment variable RMR_CONN_ASYNC=0 if blocking is desired during connections. There is no affect on the API.
2019 September 3:
- Version 1.6.0: bug fix in rmr_rts_msg() which could cause the retry of a failed rts call to "reflect" the message back rather than sending it out. Added the ability to set the applications source ID via the environment variable RMR_SRC_ID (if not set the original behaviour of using the hostname, with out any domain components) is used.
...
- Add message type constants to the RIC message type header file. Minor version bump to 1.4.0.
2019 August 16:
- Add message type constants to the RIC message type header file supported within the RMR repo. Minor version bump to 1.3.0.
2019 August 13:
- Add function rmr_get_xact() to provide a convenience function for extracting the transaction field from the message; minor version bump to 1.2.0.
2019 August 8:
- The RMR User's Guide has been added to this wiki set. See the link in the developer section below.
- RMR library version 1.1.0 is being released today. A transport status field is being added to the message buffer structure in order to provide wrapper code with access to the underlying transport provider errno value (errno is not directly available to all wrappers in all environments). This is a backwardly compatible change, but a change to the structure portion of the API, so a minor version bump was made.
2019 August 5:
- Please see the Supported Transport Mechanisms section below; support for Nanomsg is being dropped (NNG will be the only transport mechanism supported).
Current Version
1.67.0 September 317, 2019.
For a detailed description of API changes, and their related commits, please consult the CHANGES file at the top level of the RMR repo:
...