Nanomsg NG - brokerless messaging
https://nanomsg.github.io/nng/
nng (nanomsg next-generation) is a C socket library providing
several common communication patterns.
- Devel package for openSUSE:Factory
-
3
derived packages
- Links to openSUSE:Factory / nng
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout devel:libraries:c_c++/nng && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
nng-1.0.1.tar.gz | 0000541020 528 KB | |
nng-1.2.tar.gz | 0000603969 590 KB | |
nng.changes | 0000002651 2.59 KB | |
nng.spec | 0000002126 2.08 KB |
Revision 2 (latest revision is 18)
Jan Engelhardt (jengelh)
accepted
request 758860
from
Martin Hauke (mnhauke)
(revision 2)
- Update to version 1.2 This is a minor feature release of NNG. * Notably it includes support for non-SP protocol usages + for example NNG can be used to make generic websocket or HTTP applications now. * The default maximum receive size is lifted. (If you use NNG on an untrusted network, please set an explicit limit instead of relying on the defaults!) * Substantial work on performance. Most protocols should see a nice boost. * Numerous bugs fixed. - Update to version 1.1.1 This fixes a few problems with 1.1.0. * The version number at build time was misreported as 1.0.1. It will now be 1.1.1. * Support for use in CMake scenarios involving add_subdirectory * Fix for the bug report URL if NNG crashes * Fix for a crash if a remote websocket peer sends PING requests - Update to version 1.1.0 There are numerous bug fixes and improvements in this since 1.0.1. * DNS resolution is done asynchronously at dial time, leading to better self healing in the face of changing DNS records (and the possibility to use DNS for round-robin load balancing.) * Better peer identification is possible with IPC based transports. * The HTTP framework has better support for cancellation, and the HTTP client has a much friendlier ability to execute transactions. Additionally, the HTTP client can now support servers that insist on sending chunked transfer encodings. * The ZeroTier transport received a lot of work, so that it is far more stable, and supports more properties relating to peer
Comments 0