blob: f74e182bb8e09087150db142148e1224ca453364 [file] [log] [blame]
E. Scott Danielsa7610c62019-07-11 10:24:01 -04001
E. Scott Danielsb0ba22e2019-08-06 13:26:12 -04002API and build change and fixe summaries. Doc correctsions
E. Scott Danielsffba61c2019-07-29 14:28:00 -04003and/or changes are not mentioned here; see the commit messages.
E. Scott Danielsa7610c62019-07-11 10:24:01 -04004
E. Scott Danielsdfe7b622019-09-03 10:52:41 -040052019 September 3; version 1.6.0
6 Fix bug in the rmr_rts_msg() function. If a return to sender message
7 failed, the source IP address was not correctly adjusted and could
8 cause the message to be "reflected" back to the sender on a retry.
9
10 Added the ability to set the source "ID" via an environment var
11 (RMR_SRC_ID). When present in the environment, the string will
12 be placed in to the message header as the source and thus be used
13 by an application calling rmr_rts_smg() to return a response to
14 the sender. If this environment variable is not present, the host
15 name (original behaviour) is used.
16
E. Scott Daniels36262112019-08-26 10:50:52 -0400172019 August 26; version 1.4.0
18 New message types were added.
19
202019 August 16; version 1.3.0
21 New mesage types added.
22
E. Scott Daniels4ac73e32019-08-13 11:35:04 -0400232019 August 13; version 1.2.0 (API change, non-breaking)
24 The function rmr_get_xact() was added to proide a convenient
25 way to extract the transaction field from a message.
26
E. Scott Danielsf68c2ce2019-08-08 10:15:43 -0400272019 August 8; version 1.1.0 (API change)
28 This change should be backward compatable/non-breaking
29 A new field has been added to the message buffer (rmr_mbuf_t).
30 This field (tp_state) is used to communicate the errno value
31 that the transport mechanism might set during send and/or
32 receive operations. C programmes should continue to use
33 errno directly, but in some environments wrappers may not be
34 able to access errno and this provides the value to them.
35 See the rmr_alloc_msg manual page for more details.
36
E. Scott Danielsb0ba22e2019-08-06 13:26:12 -0400372019 August 6; version 1.0.45 (build changes)
38 Support for the Nanomsg transport library has been dropped.
39 The library librmr.* will no longer be included in packages.
40
41 Packages will install RMR libraries into the system preferred
42 target directory. On some systems this is /usr/local/lib
43 and on others it is /usr/local/lib64. The diretory is
44 determined by the sytem on which the package is built and
45 NOT by the system installing the package, so it's possible
46 that the RMR libraries end up in a strange location if the
47 .deb or .rpm file was generated on a Linux flavour that
48 has a different preference than the one where the package
49 is installed.
50
512019 August 6; version 1.0.44 (API change)
E. Scott Danielsdebe5042019-08-06 08:36:50 -040052 Added a new message type constant.
53
E. Scott Danielsb0ba22e2019-08-06 13:26:12 -0400542019 July 15; Version 1.0.39 (bug fix)
E. Scott Daniels6efa7aa2019-07-15 10:31:42 -040055 Prevent unnecessary usleep in retry loop.
56
E. Scott Danielsb0ba22e2019-08-06 13:26:12 -0400572019 July 12; Version 1.0.38 (API change)
E. Scott Danielsec1fc362019-07-12 15:00:28 -040058 Added new message types to RIC_message_types.h.
59
E. Scott Danielsa7610c62019-07-11 10:24:01 -0400602019 July 11; Version 1.0.37
61
E. Scott Danielsb0ba22e2019-08-06 13:26:12 -040062 librmr and librmr_nng
E. Scott Danielsa7610c62019-07-11 10:24:01 -040063 - Add message buffer API function rmr_trace_ref()
64 (see rmr_trace_ref.3 manual page in dev package).
E. Scott Danielsec1fc362019-07-12 15:00:28 -040065