Versions Compared

Old Version 32

changes.mady.by.user Scott Daniels

Saved on

compared with

New Version 33

changes.mady.by.user Scott Daniels

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Announce minor bug fix in 1.10.1 and clean up announcements to cover just the last 30 days.

...

The following are announcements related to RMR during the past 30 days; newest announcements first.

2019 October 22:

  • RMR version 1.10.1 pushed to package cloud. Bug fixes which prevent a nil message buffer pointer from being returned to the caller in the event that epoll/select cannot be initialised when using a timeout based RMR send function.   The bug was considered to have a very low probability of being triggered, and any function which tested for a nil pointer from any RMR send function would not have issues.

2019 October 7:

  • RMR version 1.10.0 pushed to package cloud.  The version reports on send counts (success/hard fail/soft fail), and attempts to reduce the number of retries reported to the user application.

...

  • NNG bug preventing reconnection of a session through docker-proxy (and maybe other proxies) was released.  A patch level change to RMR was pushed which incorporates the NNG update during the RMR build process.  (1.8.3)   This version is backwards compatible with the version of NNG which was previously used (1.1.1), but the NNG library in the run-time environment must be upgraded to avoid the proxy related bug.
  • RMR version 1.8.2 is a patch level change which fixed a bug in rmr_torcv_msg() that was causing the receive to block when the MT_CALL mode (multi-threaded call()) mode was enabled. 1.8.2 was updated on 25 September 2019.
  • RMR version 1.8.1 is a patch level change which fixed a bug: missing constant possibly needed by wrapper scripts.

2019 September 19:

  • Added three new message types; version now 1.8.0

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.  

2019 August 29:

  • Changes to eliminate the possible edge condition where the status of a successful send when the routing table has multiple round-robin groups defined for a message type was added. When there are multiple round-robin groups, a successful status (RMR_OK) will be reported if the message was sent to any of the groups.  Version bump to 1.5.0.

2019 August 26:

  • Add message type constants to the RIC message type header file. Minor version bump to 1.4.0.


Current Version

1.10.0 1 October 722,  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:

...