Version 1.6.0 Feature Release
After a very long time indeed (over 2 years!), we are happy to announce v1.6.0 of NNG!
Significant performance optimizations have been made, especially to the BUS protocol, the
nng_recvmsg()functions, when connecting and disconnecting lots of pipes,
and when using very different expiration times with vast numbers of requests.
New APIs were added for
A CMake tunable for limiting the number of threads use for request expiration is provided
Additionally various fixes for compilation problems, documentation errata, test case, and so forth
have been applied.
Version 1.5.2 Bug Fix Release
This release addresses a number of issues with 1.5.1 and 1.5.0, and users of those versions are encouraged to upgrade.
- MbedTLS 3.0 is now supported
- Several bugs in the aio subsystem leading to hangs or performance issues are addressed
- Possible crash due to mismatched nni_strdup/free usage fixed
- Fix for building on iOS, tvOS, iPadOS, watchOS
- Incorrect version number macros in CMake configuration fixed
- Several other minor cleanups (remove dead code, simplify some things)
Version 1.5.1 Bug Fix Release
Version 1.5.0 Feature Release
This release provides a two new convenience APIs, nng_msg_reserve() and nng_msg_capacity(), which can help with avoiding preallocations.
Additionally this release fixes a bug introduced in v1.4.0 where setting IPC socket permissions on Linux did not work.
Version 1.4.0 Feature Release
This is principally a performance release, as we have introduced a bunch of new features that should improve performance, especially for higher end systems (those with multiple cores will see substantially improved scalability, and lower latencies.)
- TCP ports may now be specified as service names.
- wss4, wss6, ws4, and ws6 can be used to force IPv6 or IPv4 binding for websocket URLs.
- REQ will fail fast if no retry timer is present, and the peer disconnects
- abstract sockets can be used on Linux (see nng_ipc.7 for details)
- websocket stream mode now supports TEXT mode streams
- thread names can be set, and NNG will set names for its own (see nng_thr_setname.3)
- IPv6 scoped addresses are supported
- nngcat grew --file and --data options to supply data to send
Version 1.3.2 Documentation Fixes
This release is just a set of improvements to fix some documentation bugs. These fixes are necessary for some of the automatic tooling we use for publication of documentation.
If already running v1.3.1, there is no urgency to update.
Version 1.3.1 Bug Fix Release
This is a bug fix release that rolls up a bunch of bug fixes.
- WebSocket and HTTP support for IPv6 addresses (note: IPv6 scopes are still not supported) (#844, #1224)
- Build fixes for NetBSD, OpenBSD, and Android (#1232, #1237)
- Serious framing error in TLS (regression introduced in 1.3.0) (#1235)
- nng_msg_clear was clearing the header; now it only clears the body (#1252)
- Use-after-free segfault in rep protocol (#1241)
- NNG_OPT_RECONNMAXT zero did not prevent exponential backoff (#1230)
- Use-after-free in TLS (#1239)
- Hangs in nng_close fixed (#1236, #1219)
- Fixes to ease inclusion in other projects
- Numerous minor doc bugs fixed
- Various test suite bugs fixed
Also there are two minor feature enhancements:
- Support for obtaining the peer process ID using IPC on modern macOS
- nngcat now supports data from standard input when the file is specified as "-" (#1007)
It is recommended that all users using v1.3.0 upgrade to v1.3.1.
Support for TLS 1.3 and external TLS providers.
There is now an API whereby external "
engines" can be developed
for different TLS implementations. The first of these, for wolfSSL,
is available. Set this with the
The default is still to use Mbed TLS. The wolfSSL plugin is
available under a different license (GPLv3 or commercial), and also
provides support for TLS 1.3 and FIPS 140-2 capable solutions.
Message cloning and related performance improvements. This is not
a feature, so much as a rather large improvement in terms of performance.
All workloads will see some benefit -- some will see substantial benefits.
Numerous other performance improvements. Much effort was made to
reducing allocations, improving cache effectiveness, and eliminating
extra context switches. This work is not yet done, but this is a big
step in the right direction.
HTTP Server support for "non-exclusive" registration -- a given handler
may be registered as a fallback handler (e.g. for a directory), even if
more specific handlers are registered.
Performance test programs grew more options to select different
protocols and to change the URL to test across different transports.
Notable Bug Fixes
Thread count is limited.
Previously we would spawn potentially vast numbers of threads based on the
number of available cores. By default we set an upper limit on this that
is about 20 threads. Tune this with the
Raw mode fixes for XREQ and XRESPONDENT. These protocols used the raw mode
inconsistently, leaving the header in the message body. This is corrected
and the protocol headers are kept in the message headers. There is some small
risk that some applications broken, but we are not aware of any that used
RAW mode to parse message headers.
HTTP Server root URL handling had a few issues which are resolved.
Some platforms had difficult building due to inconsistencies in the
handling of atomics.
Numerous test suites uncovered small (rare) races, etc. The tests
themselves were often racy. Fixes to both NNG and the tests have been
made, while increasing overall test coverage.
REP protocol with SENDFD was inconsistent (#1088).
Polyamorous Pair v1 mode is changed, such that a new API call is needed
to use it. Further, this mode will likely be removed in a future release.
Note that this mode also does not work with other implementations, nor
does it support operation with
Maximum hop count across
nng_device()proxies is now limited to 15.
This limit should be sufficient for all reasonable configurations,
and forcing this allowed us to to inline the header for performance
The nng_msg_options support was removed. It was not used for anything.
Version 1.2.6 Bug Fix Release
This is another release to fix builds for older compiles without support for C11 atomics.
If you were able to build prior releases, there is no need to update to this release. Generally speaking, the use of older compilers will give less than ideal results; if at all possible upgrading to modern compilers is strongly recommended. The performance different is likely to be significant.