2 API and build change and fix summaries. Doc correctsions
3 and/or changes are not mentioned here; see the commit messages.
5 2019 December 9; version 1.13.1
6 Correct documentation and missing rel-notes update for RTD.
8 2019 December 6; version 1.13.0
9 Add ability to route messages based on the MEID in a message combined
10 with the message type/subscription-ID.
13 2019 November 14; version 1.11.1 (Amber)
14 Fix bug in payload reallocation function; correct length of payload
15 was not always copied.
17 2019 November 13; version 1.12.1
18 New message type constants added to support A1.
20 2019 November 4; version 1.11.0 (Amber)
21 Version bump to move away from the 1.10.* to distinguish between
22 release A and the trial.
24 2019 November 7; version 1.12.0
25 Version cut to support continued development for next release
26 preserving the 1.11.* versions for release 1 (Amber) and
29 2019 October 31; version 1.10.2
30 Provide the means to increase the payload size of a received message
31 without losing the data needed to use the rmr_rts_msg() funciton.
33 2019 October 21; version 1.10.1
34 Fix to prevent null message buffer from being returned by the timeout
35 receive function if the function is passed one to reuse.
37 2019 October 21; version 1.10.1
38 Add periodic dump of send count info to stderr.
40 2019 September 27; version 1.9.0
41 Python bindings added receive all queued function and corrected a unit test
43 2019 September 25; version 1.8.3
44 Correct application level test issue causing timing problems during
45 jenkins verification testing at command and merge
47 Handle the NNG connection shutdown status which may now be
48 generated when a connection throug a proxy is reset.
50 2019 September 25; version 1.8.2
51 Correct bug in rmr_torcv_msg() when timeout set to zero (0).
53 2019 September 19; version 1.8.1
54 Correct missing constant for wrappers.
56 2019 September 19; version 1.8.0
57 New message types added:
58 RAN_CONNECTED, RAN_RESTARTED, RAN_RECONFIGURED
60 2019 September 17; version 1.7.0
61 Initial connection mode now defaults to asynchronous. Set RMR_ASYNC_CONN=0
62 in the environment before rmr_init() is invoked to revert to
63 synchronous first TCP connections. (Recovery connection attempts
64 have always been asynchronous).
66 2019 September 3; version 1.6.0
67 Fix bug in the rmr_rts_msg() function. If a return to sender message
68 failed, the source IP address was not correctly adjusted and could
69 cause the message to be "reflected" back to the sender on a retry.
71 Added the ability to set the source "ID" via an environment var
72 (RMR_SRC_ID). When present in the environment, the string will
73 be placed in to the message header as the source and thus be used
74 by an application calling rmr_rts_smg() to return a response to
75 the sender. If this environment variable is not present, the host
76 name (original behaviour) is used.
78 2019 August 26; version 1.4.0
79 New message types were added.
81 2019 August 16; version 1.3.0
82 New mesage types added.
84 2019 August 13; version 1.2.0 (API change, non-breaking)
85 The function rmr_get_xact() was added to proide a convenient
86 way to extract the transaction field from a message.
88 2019 August 8; version 1.1.0 (API change)
89 This change should be backward compatable/non-breaking
90 A new field has been added to the message buffer (rmr_mbuf_t).
91 This field (tp_state) is used to communicate the errno value
92 that the transport mechanism might set during send and/or
93 receive operations. C programmes should continue to use
94 errno directly, but in some environments wrappers may not be
95 able to access errno and this provides the value to them.
96 See the rmr_alloc_msg manual page for more details.
98 2019 August 6; version 1.0.45 (build changes)
99 Support for the Nanomsg transport library has been dropped.
100 The library librmr.* will no longer be included in packages.
102 Packages will install RMR libraries into the system preferred
103 target directory. On some systems this is /usr/local/lib
104 and on others it is /usr/local/lib64. The diretory is
105 determined by the sytem on which the package is built and
106 NOT by the system installing the package, so it's possible
107 that the RMR libraries end up in a strange location if the
108 .deb or .rpm file was generated on a Linux flavour that
109 has a different preference than the one where the package
112 2019 August 6; version 1.0.44 (API change)
113 Added a new message type constant.
115 2019 July 15; Version 1.0.39 (bug fix)
116 Prevent unnecessary usleep in retry loop.
118 2019 July 12; Version 1.0.38 (API change)
119 Added new message types to RIC_message_types.h.
121 2019 July 11; Version 1.0.37
123 librmr and librmr_nng
124 - Add message buffer API function rmr_trace_ref()
125 (see rmr_trace_ref.3 manual page in dev package).