8 commits
Author | SHA1 | Message | Date | |
---|---|---|---|---|
adam
|
c9165e4b9a |
zeromq: updated to 4.2.3
version 4.2.3 stable: * API change: previously ZMQ_POLLOUT on a ZMQ_ROUTER socket returned always true due to how the type works. When ZMQ_ROUTER_MANDATORY is set, sending fails when the peer is not available, but ZMQ_POLLOUT always returns true anyway, which does not make sense. Now when ZMQ_ROUTER_MANDATORY is set, ZMQ_POLLOUT on a ZMQ_ROUTER will return true only if at least one peer is available. Given ZMQ_POLLOUT with ZMQ_ROUTER was not usable at all previously, we do not consider this a breakage warranting a major or minor version increase. * ZMQ_IDENTITY has been renamed to ZMQ_ROUTING_ID and ZMQ_CONNECT_RID has been renamed to ZMQ_CONNTECT_ROUTING_ID to disambiguate. ZMQ_IDENTITY and ZMQ_CONNECT_RID are still available to keep backward compatibility, and will be removed in a future release after further advance notice. * DRAFT API change: zmq_poller_wait, zmq_poller_wait_all and zmq_poller_poll have been changed to be inline with other existing APIs that have a timeout to return EAGAIN instead of ETIMEDOUT as the errno value. * Existing non-DRAFT socket types ZMQ_REP/REQ, ZMQ_ROUTER/DEALER and ZMQPUB/SUB, that were previously declared deprecated, have been reinstated as stable and supported. * Tweetnacl: add support for, and use preferably if available, getrandom() as a simpler and less error-prone alternative to /dev/urandom on OSes where it is available (eg: Linux 3.18 with glibc 2.25). * Curve: all remaining traces of debug output to console are now removed, and new DRAFT events are available to properly debug CURVE, PLAIN, GSSAPI and ZAP events and failures. See below for details on the new events. * New DRAFT (see NEWS for 4.2.0) socket options: - ZMQ_GSSAPI_PRINCIPAL_NAMETYPE and ZMQ_GSSAPI_SERVICE_PRINCIPAL_NAMETYPE, for the corresponding GSSAPI features. Additional definitions for principal name types: - ZMQ_GSSAPI_NT_HOSTBASED - ZMQ_GSSAPI_NT_USER_NAME - ZMQ_GSSAPI_NT_KRB5_PRINCIPAL See doc/zmq_gssapi.txt for details. - ZMQ_BINDTODEVICE (Linux only), which will bind the socket(s) to the specified interface. Allows to use Linux VRF, see: https://www.kernel.org/doc/Documentation/networking/vrf.txt NOTE: requires the program to be ran as root OR with CAP_NET_RAW - ZMQ_ZAP_ENFORCE_DOMAIN, enables strict RFC 27 compatibility mode and makes the ZAP Domain mandatory when using security. See: https://rfc.zeromq.org/spec:27/ZAP See doc/zmq_setsockopt.txt and doc/zmq_getsockopt.txt for details. * New DRAFT (see NEWS for 4.2.0) context options: - ZMQ_THREAD_AFFINITY_CPU_ADD and ZMQ_THREAD_AFFINITY_CPU_REMOVE (Posix only), to add and remove CPUs to the affinity set of the I/O threads. Useful to pin the background threads to specific CPUs. - ZMQ_THREAD_NAME_PREFIX (Posix only), to add a specific integer prefix to the background threads names, to easily identify them for debugging purposes. See doc/zmq_ctx_set.txt and doc/zmq_ctx_get.txt for details. * New DRAFT (see NEWS for 4.2.0) message property name definitions to facilitate the use of zmq_msg_gets: - ZMQ_MSG_PROPERTY_ROUTING_ID - ZMQ_MSG_PROPERTY_SOCKET_TYPE - ZMQ_MSG_PROPERTY_USER_ID - ZMQ_MSG_PROPERTY_PEER_ADDRESS See doc/zmq_msg_gets.txt for details. * New DRAFT (see NEWS for 4.2.0) API zmq_socket_get_peer_state, to be used to query the state of a specific peer (via routing-id) of a ZMQ_ROUTER socket. * New DRAFT (see NEWS for 4.2.0) Socket Monitor events: - ZMQ_EVENT_HANDSHAKE_FAILED_NO_DETAIL, unknown system error and returns errno - ZMQ_EVENT_HANDSHAKE_SUCCEEDED, handshake was successful - ZMQ_EVENT_HANDSHAKE_FAILED_PROTOCOL, protocol errors between peers or server and ZAP handler. Returns one of ZMQ_PROTOCOL_ERROR_* - see manpage for list - ZMQ_EVENT_HANDSHAKE_FAILED_AUTH, failed authentication, returns ZAP status These events trigger when the ZMTP security mechanism handshake is completed or failed. See doc/zmq_socket_monitor.txt for more information. * New DRAFT (see NEWS for 4.2.0) zmq_proxy_steerable command 'STATISTICS' to retrieve stats about the amount of messages and bytes sent and received by the proxy. See doc/zmq_proxy_steerable.txt for more information. * Add new autoconf --disable-libunwind option to stop building with libunwind even if it is available. * Add new autoconf --disable-Werror option to avoid building with the Werror flag. * Use pkg-config as the first method for finding and building with external optional dependencies such as libnorm, libpgm and gssapi. * On Posix platform where the feature is available, name the ZMQ background threads to simplify debugging: "ZMQbg/<num_thread>" * Improve performance of zmq_poller_* (and zmq_poll and zmq_proxy when building with DRAFT APIs enabled). * The TCP unit tests have been refactored to bind and connect to random ports rather than hard-coded ones, to allow running tests in parallel. There are 6 exceptions where it is necessary to use an hard-coded port to test specific code paths that would not be exercised when binding to a wildcard port. These are listed in tests/testutil.hpp so that distributions can easily patch them if they wish to and so that they can be unique across all the tests, allowing parallel runs. The IPC unit tests have been changed as well to use unique socket file names per test, where before there were some clashes. * Fixed 2349 - fix building with libsodium when using CMake * Fixed 2334 - do not assert when tuning socket options fails due to network errors, but simply retry again when connecting or send a socket monitor ZMQ_EVENT_ACCEPT_FAILED event when binding * Fixed 2341 - fix source files path in VS2015 solution * Fixed 2344 - Note that on Windows with VS2012 it is mandatory to increase the default stack size to at least 2MB * Fixed 2348 - ZMQ_ROUTER send with ZMQ_ROUTER_MANDATORY can be stuck in case of network problem * Fixed 2358 - occasional abort on zmq_connect on Windows * Fixed 2370 - zmq_curve_keypair should return an error on failure rather than ignoring them and always returning 0 * Fixed 2452 - __STDC_LIMIT_MACROS before precompiled headers causes VC++ warning * Fixed 2457 - fix building with libsodium in Visual Studio solutions * Fixed 2466 - add const qualifier to internal and public API that does not modify parameters * Fixed 2471 - do more checks for OOM conditions when dynamic allocations is used * Fixed 2476 - assertion causes abort after ZAP stop at shutdown * Fixed 2479 - improve zmq_poller performance on Windows * Fixed 2481 - potential memory leaks due to ZMTP handshake failures * Fixed 2531 - ZMQ_GSSAPI_PRINCIPAL sockopt has no effect on client side * Fixed 2535 - add BUILD_SHARED and BUILD_STATIC options to CMake, both on by default, to toggle shared and static library builds * Fixed 2537 - use SYSTEM_CLOCK on OSX and CLOCK_MONOTONIC elsewhere for internal timers to avoid races * Fixed 2540 - new zmq_poller used by zmq_poll without DRAFTs * Fixed 2552 - Fix WITH_DOC CMake build to avoid checking for asciidoc if the option is disabled * Fixed 2567 - Memory leak in REP socket handling * Fixed 2579 - Compilation issue on Windows with CMake + ninja * Fixed 2588 - SIGBUS under 64-bit SunOS Sparc * Fixed 2590 - crash when using ZMQ_IMMEDIATE and ZMQ_LINGER to non-zero * Fixed 2601 - XPUB_MANUAL subscriptions not removed on peer term * Fixed 2602 - intermittent memory leak for ZMQ_REQ/REP send/recv * Fixed 2608 - CURVE server (connect) fails when client rebinds * Fixed 2610 - print backtraces in mutual exclusion to avoid mixing different traces * Fixed 2621 - add missing CMake files to distributable tarball * Fixed 2630 - improve compatibility with OpenBSD w.r.t. IPV6_V6ONLY * Fixed 2638 - note in INSTALL that when using Windows builds on Linux with Wine it is necessary to increase the minimum TCP buffers * Fixed 2632 - Fix file descriptor leak when using Tweetnacl (internal NACL implementation) instead of Libsodium, and fix race condition when using multiple ZMQ contexts with Tweetnacl * Fixed 2681 - Possible buffer overflow in CURVE mechanism handshake. NOTE: this was protected by an assert previously, so there is no security risk. * Fixed 2704 - test_sockopt_hwm fails occasionally on Windows * Fixed 2701 - pgm build via cmake doesn't link libzmq with libpgm * Fixed 2711 - ZAP handler communication errors should be handled consistently * Fixed 2723 - assertion in src\select.cpp:111 or hang on zmq_ctx_destroy on Windows * Fixed 2728 - fix support O_CLOEXEC when building with CMake * Fixed 2761 - improve compatibility with TrueOS (FreeBSD 12) * Fixed 2764 - do not unlink IPC socket files when closing a socket to avoid race conditions * Fixed 2770 - support lcov 1.13 and newer * Fixed 2787 - add libiphlpapi to PKGCFG_LIBS_PRIVATE for static mingw builds * Fixed 2788 - document that adding -DZMQ_STATIC is required for Windows static builds with Mingw * Fixed 2789 - description of zmq_atomic_counter_value return value is cloned from zmq_atomic_counter_new * Fixed 2791 - fix building with DRAFT APIs on CentOS 6 * Fixed 2794 - router_t methods should not allocate memory for lookup in outpipes * Fixed 2809 - optimize select() usage on Windows * Fixed 2816 - add CMake and autoconf check for accept4, as it is not available on old Linux releases, and fallback to accept + FD_CLOEXEC * Fixed 2824 - ZMQ_REQ socket does not report ZMQ_POLLOUT when ZMQ_REQ_RELAXED is set * Fixed 2827 - add support for Haiku * Fixed 2840 - fix building with VS2008 * Fixed 2845 - correct the ZMQ_LINGER documentation to accurately reflect that the default value is -1 (infinite). It never was 30 second in any released version, it was only changed briefly and then changed back, but the manpage was not reverted. * Fixed 2861 - CMake/MSVC: export ZMQ_STATIC when needed. |
||
fhajny
|
5ab124e05e |
Update net/zeromq to 4.2.1.
0MQ version 4.2.1 stable, released on 2016/12/31 ============================================= * New DRAFT (see NEWS for 4.2.0) Socket Monitor events: - ZMQ_EVENT_HANDSHAKE_SUCCEED - ZMQ_EVENT_HANDSHAKE_FAILED These events trigger when the ZMTP security mechanism handshake is completed. See doc/zmq_socket_monitor.txt for more information. * New DRAFT (see NEWS for 4.2.0) Context options: - ZMQ_MSG_T_SIZE See doc/zmq_ctx_get.txt for more information. * Fixed #2268 - improved compatibility with mingw32 * Fixed #2254 - ZMQ_PUB compatibility with libzmq 2.x broken * Fixed #2245 - added support for VS2017, Windows SDK 10.0.14393.0, toolset v141 * Fixed #2242 - file descriptors leaks on fork+exec * Fixed #2239 - retired poller item crash from reaper thread * Fixed #2234 - improved compatibility with AIX 7.1 * Fixed #2225 - cannot pick select for poller * Fixed #2217 - CMake build uses library version as the ABI version * Fixed #2208 - added support for ZMQ_TOS on IPv6 * Fixed #2200 - no documentation for ZMQ_SOCKS_PROXY * Fixed #2199 - no documentation for zmq_curve_public * Fixed #2196 - fixed build and runtime errors on kFreeBSD 0MQ version 4.2.0 stable, released on 2016/11/04 ============================================= * For Pieter. Thanks for making all of this possible. "Tell them I was a writer. A maker of software. A humanist. A father. And many things. But above all, a writer. Thank You. :)" - Pieter Hintjens * This release introduces new APIs, but it is ABI compatible with libzmq 4.1.2 and up. * Note for ARM and SPARC users: an alignment problem in zmq_msg_t that could in some cases and on some CPUs cause a SIGBUS error was solved, but it requires a rebuild of your application against the 4.2.0 version of include/zmq.h. To clarify, this change does not affect the internals of the library but only the public definition of zmq_msg_t, so there is no ABI incompatibility. * Security with Curve is now available by default thanks to Tweetnacl sources: https://tweetnacl.cr.yp.to/index.html Libsodium is still fully supported but has to be enabled with the build flag --with-libsodium. Distribution and package maintainers are encouraged to use libsodium so that the security implementation can be audited and maintained separately. * New Context options: - ZMQ_MAX_MSGSZ - ZMQ_BLOCKY See doc/zmq_ctx_set.txt and doc/zmq_ctx_get.txt for details. * New Socket options: - ZMQ_HANDSHAKE_IVL - ZMQ_SOCKS_PROXY - ZMQ_XPUB_NODROP - ZMQ_XPUB_MANUAL - ZMQ_XPUB_WELCOME_MSG - ZMQ_STREAM_NOTIFY - ZMQ_INVERT_MATCHING - ZMQ_HEARTBEAT_IVL - ZMQ_HEARTBEAT_TTL - ZMQ_HEARTBEAT_TIMEOUT - ZMQ_XPUB_VERBOSER - ZMQ_CONNECT_TIMEOUT - ZMQ_TCP_MAXRT - ZMQ_THREAD_SAFE - ZMQ_MULTICAST_MAXTPDU - ZMQ_VMCI_BUFFER_SIZE - ZMQ_VMCI_BUFFER_MIN_SIZE - ZMQ_VMCI_BUFFER_MAX_SIZE - ZMQ_VMCI_CONNECT_TIMEOUT - ZMQ_USE_FD See doc/zmq_setsockopt.txt and doc/zmq_getsockopt.txt for details. * New CURVE helper function to derive z85 public key from secret key: zmq_curve_public * New cross-platform atomic counter helper functions: zmq_atomic_counter_new, zmq_atomic_counter_set, zmq_atomic_counter_inc, zmq_atomic_counter_dec, zmq_atomic_counter_value, zmq_atomic_counter_destroy See doc/zmq_atomic_*.txt for details. * New DRAFT APIs early-release mechanism. New APIs will be introduced early in public releases, and until they are stabilized and guaranteed not to change anymore they will be unavailable unless the new build flag --enable-drafts is used. This will allow developers and early adopters to test new APIs before they are finalized. NOTE: as the name implies, NO GUARANTEE is made on the stability of these APIs. They might change or disappear entirely. Distributions are recommended NOT to build with them. New socket types have been introduced in DRAFT state: ZMQ_SERVER, ZMQ_CLIENT, ZMQ_RADIO, ZMQ_DISH, ZMQ_GATHER, ZMQ_SCATTER, ZMQ_DGRAM All these sockets are THREAD SAFE, unlike the existing socket types. They do NOT support multipart messages (ZMQ_SNDMORE/ZMQ_RCVMORE). ZMQ_RADIO, ZMQ_DISH and ZMQ_DGRAM also support UDP as transport, both unicast and multicast. See doc/zmq_udp.txt for more details. New methods to support the new socket types functionality: zmq_join, zmq_leave, zmq_msg_set_routing_id, zmq_msg_routing_id, zmq_msg_set_group, zmq_msg_group See doc/zmq_socket.txt for more details. New poller mechanism and APIs have been introduced in DRAFT state: zmq_poller_new, zmq_poller_destroy, zmq_poller_add, zmq_poller_modify, zmq_poller_remove, zmq_poller_wait, zmq_poller_wait_all, zmq_poller_add_fd zmq_poller_modify_fd, zmq_poller_remove_fd and a new supporting struct typedef: zmq_poller_event_t They support existing socket type, new thread-safe socket types and file descriptors (cross-platform). Documentation will be made available in the future before these APIs are declared stable. New cross-platform timers helper functions have been introduced in DRAFT state: zmq_timers_new, zmq_timers_destroy, zmq_timers_add, zmq_timers_cancel, zmq_timers_set_interval, zmq_timers_reset, zmq_timers_timeout, zmq_timers_execute and a new supporting callback typedef: zmq_timer_fn * Many, many bug fixes. The most important fixes are backported and captured in the 4.1.x and 4.0.x changelogs. 0MQ version 4.2.0 rc1, released on 2016/11/01 ============================================= * Many changes, see ChangeLog. 0MQ version 4.1.6 stable, released on 2016/11/01 ================================================ * Fixed #2051 - getifaddrs can fail with ECONNREFUSED * Fixed #2091 - testutil.hpp fails to build on Windows XP * Fixed #2096 - add tests/CMakeLists.in and version.rc.in to dist tar * Fixed #2107 - zmq_connect with IPv6 "source:port;dest:port" broken * Fixed #2117 - ctx_term assert with inproc zmq_router connect-before-bind * Fixed #2158 - Socket monitor uses internal Pair from multiple threads * Fixed #2161 - messages dropped due to HWM race * Fixed #1325 - alignment issue with zmq_msg_t causes SIGBUS on SPARC and ARM 0MQ version 4.1.5 stable, released on 2016/06/17 ================================================ * Fixed #1673 - CMake on Windows put PDB in wrong directory. * Fixed #1723 - Family is not set when resolving NIC on Android. * Fixed #1608 - Windows 7 TCP slow start issue. * Fixed #1806 - uninitialised read in curve getsockopt. * Fixed #1807 - build broken with GCC 6. * Fixed #1831 - potential assertion failure with latest libsodium. * Fixed #1850 - detection issues with tweetnacl/libsodium. * Fixed #1877 - Avoid terminating connections prematurely * Fixed #1887 - zmq_bind IPv4 fallback still tries IPv6 * Fixed #1866 - fails to build on SunOS 5.10 / Solaris 10 * Fixed #919 - ZMQ_LINGER (related to #1877) * Fixed #114 - cannot unbind with same endpoint with IPv6 enabled. * Fixed #1952 - CMake scripts not part of release tarballs * Fixed #1542 - Fix a crash on Windows when port 5905 is in use. * Fixed #2021 - Fix building on sparc32. |
||
he
|
cfd62044a4 |
Update to zeromq version 4.1.3, currently latest stable release.
Pkgsrc changes: * Adapt PLIST Upstream changes: 0MQ version 4.1.3 stable, released on 2015/08/17 * Fixed #1532 - getsockopt ZMQ_RCVMORE now resets all bits instead of only 32 * Fixed #1445 - zmq::socket_base_t::connect fails on tcp ipv6 address 0MQ version 4.1.2 stable, released on 2015/06/15 * Added explicit reference to static link exception in every source file. * Bumped ABI version to 5:0:0 since 4.1.x changed the ABI. * Fixed STDINT event interface macros to work with CZMQ 3.0. * Fixed installation of man pages when BUILD_DOC is not set. * Fixed #1428 - regression on single-socket proxies. 0MQ version 4.1.1 stable, released on 2015/06/02 * Fixed #1208 - fix recursion in automake packaging. * Fixed #1224 - crash when processing empty unsubscribe message. * Fixed #1213 - properties files were missing from source packages. * Fixed #1273 - V3 protocol handler vulnerable to downgrade attacks. * Fixed #1347 - lack way to get peer address. * Fixed #1362 - SUB socket sometimes fails to resubscribe properly. * Fixed #1377, #1144 - failed with WSANOTINITIALISED in some cases. * Fixed #1389 - PUB, PUSH sockets had slow memory leak. * Fixed #1382 - zmq_proxy did not terminate if there were no readers. 0MQ version 4.0.8 stable, released on 2015/07/xx * Fixed LIBZMQ-949 - zmq_unbind fails for inproc and wildcard endpoints 0MQ version 4.0.7 stable, released on 2015/06/15 * Fixed #1428 - regression on single-socket proxies. 0MQ version 4.0.6 stable, released on 2015/06/02 * Fixed #1273 - V3 protocol handler vulnerable to downgrade attacks. * Fixed #1362 - SUB socket sometimes fails to resubscribe properly. * Fixed #1377, #1144 - failed with WSANOTINITIALISED in some cases. * Fixed #1389 - PUB, PUSH sockets had slow memory leak. * Fixed #1382 - zmq_proxy did not terminate if there were no readers. |
||
obache
|
3b87ba0f5c |
Update zeromq to 4.0.5.
0MQ version 4.0.5 stable, released on 2014/10/14 ================================================ * Fixed #1191; CURVE mechanism does not verify short term nonces. * Fixed #1190; stream_engine is vulnerable to downgrade attacks. * Fixed #1088; assertion failure for WSAENOTSOCK on Windows. * Fixed #1015; race condition while connecting inproc sockets. * Fixed #994; bump so library number to 4.0.0 * Fixed #939, assertion failed: !more (fq.cpp:99) after many ZAP requests. * Fixed #872; lost first part of message over inproc://. * Fixed #797, keep-alive on Windows. |
||
obache
|
b05f734295 |
Update zeromq to 4.0.3.
0MQ version 4.0.3 stable, released on 2013/11/24 ================================================ Bug Fixes --------- * Fixed test_many_sockets case, which failed when process socket limit was 1024. 0MQ version 4.0.2 stable, released on 2013/11/24 ================================================ Bug Fixes --------- * Fixed LIBZMQ-583 - improved low-res timer for Windows * Fixed LIBZMQ-578 - z85_decode was extremely slow * Fixed LIBZMQ-577 - fault in man pages. * Fixed LIBZMQ-574 - assertion failure when ran out of system file handles * Fixed LIBZMQ-571 - test_stream failing in some cases * Fixed LIBZMQ-569 - Socket server crashes with random client data and when talking to 2.2 versions * Fixed LIBZMQ-39 - Bad file descriptor during shutdown * Pulled expected failing test_linger.cpp from release * Reduced pause time in tests to allow "make check" to run faster 0MQ version 4.0.1 stable, released on 2013/10/08 ================================================ Changes ------- * Updated CURVE mechanism to track revised RFC 27 (INITIATE vouch). The INITIATE command vouch box is Box[C',S](C->S') instead of Box[C'](C->S), to reduce the risk of client impersonation, as per https://codesinchaos.wordpress.com/2012/09/09/curvecp-1/. * Fixed LIBZMQ-567, adding abstract namespaces for IPC sockets on Linux. Converts an initial strudel or "at sign" (@) in the Unix socket path to a NULL character ('\0') indicating that the socket uses the abstract namespace instead of the filesystem namespace. For instance, binding a socket to 'ipc://@/tmp/tester' will not create a file associated with the socket whereas binding to 'ipc:///tmp/tester' will create the file /tmp/tester. See issue 567 for more information. * Added zmq_z85_encode and zmq_z85_decode to core libzmq API. * Added zmq_curve_keypair to core libzmq API. * Bumped library ABI version to 4:0:1. Bug fixes --------- * Fixed some build/test errors on OS/X + Clang++. * Fixed LIBZMQ-565, typo in code. * Fixed LIBZMQ-566, dealer-to-router connections sometimes failing. * Fixed builds for AIX, MSVC 2008, OS/X with clang++, Solaris. * Improved CURVE handshake error handling. 0MQ version 4.0.0 (RC1), released on 2013/09/20 =============================================== Major changes ------------- * New wire level protocol, ZMTP/3.0, see http://rfc.zeromq.org/spec:23. Does not yet implement the SUBSCRIBE, CANCEL, PING, and PONG commands. * New security framework, from plain user+password to strong encryption, see section below. See http://hintjens.com/blog:49 for a tutorial. * New ZMQ_STREAM socket type for working as a TCP client or server. See: tests/test_stream.cpp. Improvements ------------ * You can now connect to an inproc:// endpoint that does not already exist. This means inproc:// no longer needs careful set-up, but it may break code that relied on the old behaviour. See: tests/test_inproc_connect.cpp. * Libzmq now checks socket types at connection time, so that trying to connect a 'wrong' socket type will fail. * New zmq_ctx_shutdown API method will shutdown a context and send ETERM to blocking calls, without blocking. Use zmq_ctx_term to finalise the process. * The regression test suite has been significantly extended and improved. * Contexts can now be terminated in forked child processes. See: tests/test_fork.cpp. * zmq_disconnect now respects the linger setting on sockets. * New zmq_send_const API method to send constant data (without copying). See: tests/test_inproc_connect.cpp. * Added CMake support for static libraries. * Added test cases for socket semantics as defined in RFCs 28, 29, 30, 31. See: tests/test_spec_*.cpp. * New socket option, ZMQ_PROBE_ROUTER triggers an empty message on connect. See: tests/test_probe_router.cpp. * New socket option, ZMQ_REQ_CORRELATE allows for correlation of replies from a REP socket. See: tests/test_req_correlate.cpp. * New socket option, ZMQ_REQ_RELAXED, lets you disable the state machine on a REQ socket, so you can send multiple requests without waiting for replies, and without getting an EFSM error. See: tests/test_req_relaxed.cpp. * New socket option, ZMQ_CONFLATE restricts the outgoing and incoming socket buffers to a single message. See: tests/test_conflate.cpp. Deprecated Options ------------------ * ZMQ_IPV4ONLY deprecated and renamed to ZMQ_IPV6 so that options are consistently "off" by default. * ZMQ_DELAY_ATTACH_ON_CONNECT deprecated, and renamed to ZMQ_IMMEDIATE. See: tests/test_immediate.cpp. Security Framework ------------------ Based on new ZMTP wire level protocol that negotiates a security "mechanism" between client and server before exchanging any other data. Security mechanisms are extensible. ZMTP defines three by default: * NULL - classic ZeroMQ, with no authentication. See http://rfc.zeromq.org/spec:23. * PLAIN - plain-text username + password authentication. See http://rfc.zeromq.org/spec:24. * CURVE - secure authentication and encryption based on elliptic curve cryptography, using the Curve25519 algorithm from Daniel Bernstein and based on CurveCP's security handshake. See http://rfc.zeromq.org/spec:25, http://rfc.zeromq.org/spec:26, and http://curvecp.org. Authentication is done by pluggable "authenticators" that connect to libzmq over an inproc endpoint, see http://rfc.zeromq.org/spec:27. Socket options to configure PLAIN security on client or server: * ZMQ_PLAIN_SERVER, ZMQ_PLAIN_USERNAME, ZMQ_PLAIN_PASSWORD. See tests/test_security_plain. Socket options to configure CURVE security on client or server: * ZMQ_CURVE_SERVER, ZMQ_CURVE_PUBLICKEY, ZMQ_CURVE_SECRETKEY, ZMQ_CURVE_SERVERKEY. See tests/test_security_curve.cpp. Socket options to configure "domain" for ZAP handler: * ZMQ_ZAP_DOMAIN, see tests/test_security_null.cpp. Support for encoding/decoding CURVE binary keys to ASCII: * zmq_z85_encode, zmq_z85_decode. Other issues addressed in this release -------------------------------------- * LIBZMQ-525 Multipart upstreaming from XSUB to XPUB |
||
adam
|
8910bfaeee |
Changes 3.2.3:
* LIBZMQ-526 Assertion failure "Invalid argument (tcp_connecter.cpp:285)" * LIBZMQ-446 Setting the DSCP bits by default causes CAP_NET_ADMIN error * LIBZMQ-496 Crash on heavy socket opening/closing: Device or resource busy (mutex.hpp:90) * LIBZMQ-462 test_connect_delay fails at test_connect_delay.cpp:80 * LIBZMQ-497 Messages getting dropped * LIBZMQ-488 signaler.cpp leaks the win32 Event Handle * LIBZMQ-476 zmq_disconnect has no effect for inproc sockets * LIBZMQ-475 zmq_disconnect does not sent unsubscribe messages |
||
obache
|
9e37e75ff1 |
Update zeromq to 2.1.6.
0MQ version 2.1.6 (Stable), released on 2011/04/26 ================================================== Bug fixes --------- * Fixed memory leak with threads on Windows. * Assert during SUB socket termination fixed. Changes ------- * Checks zmq_msg_t validity at each operation. * Inproc performance tests now work on Windows. * PGM wire format specification improved in zmq_pgm(7) * Added thread latency/throughput performance examples. * Added "--with-system-pgm" configure option to use already installed OpenPGM. 0MQ version 2.1.5 (Broken), released on 2011/04/20 ================================================== Note that this version contained a malformed patch and is not usable. It is not available for download, but is available in the git via the 2.1.5 tag. 0MQ version 2.1.4 (Stable), released on 2011/03/30 ================================================== Bug fixes --------- * Fix to OpenPGM which was asserting on small messages (Steven McCoy). Changes ------- * Upgraded OpenPGM to version 5.1.115 (Pieter Hintjens). * OpenPGM build changed to not install OpenPGM artifacts. 0MQ version 2.1.3 (Stable), released on 2011/03/21 ================================================== Bug fixes --------- * Fix to PUSH sockets, which would sometimes deliver tail frames of a multipart message to new subscribers (Martin Sustrik). * Fix to PUB sockets, which would sometimes deliver tail frames of a multipart message to new subscribers (Martin Sustrik). * Windows build was broken due to EPROTONOSUPPORT not being defined. This has now been fixed (Martin Sustrik). * Various fixes to make OpenVMS port work (Brett Cameron). * Corrected Reference Manual to note that ZMQ_LINGER socket option may be set at any time, not just before connecting/binding (Pieter Hintjens). * Fix to C++ binding to properly close sockets (Guido Goldstein). * Removed obsolete assert from pgm_socket.cpp (Martin Sustrik). Changes ------- * Removed stand-alone devices (/devices subdirectory) from distribution. These undocumented programs remain available in older packages (Pieter Hintjens). * OpenPGM default rate raised to 40mbps by default (Steven McCoy). * ZMQ_DEALER and ZMQ_ROUTER macros provided to ease upgrade to 0MQ/3.0. These are scheduled to replace ZMQ_XREQ and ZMQ_XREP (Pieter Hintjens). * Added man page for zmq_device(3) which was hereto undocumented (Pieter Hintjens). * Removed zmq_queue(3), zmq_forwarder(3), zmq_streamer(3) man pages (Pieter Hintjens). OpenPGM Integration ------------------- * Upgraded OpenPGM to version 5.1.114 (Steven McCoy, Mikko Koppanen). * Build system now calls OpenPGM build process directly, allowing easier future upgrades of OpenPGM (Mikko Koppanen). * Build system allows configuration with arbitrary versions of OpenPGM (./configure --with-pgm=libpgm-x.y.z) (Mikko Koppanen). * OpenPGM uses new PGM_ODATA_MAX_RTE controlling original data instead of PGM_TXW_MAX_RTE covering entire channel (Steven McCoy). Building -------- * 0MQ builds properly on FreeBSD (Mikko Koppanen). 0MQ version 2.1.2 (rc2), released on 2011/03/06 =============================================== Bug fixes --------- * 0MQ now correctly handles durable inproc sockets; previously it ignored explicit identities on inproc sockets. * Various memory leaks were fixed. * OpenPGM sender/receiver creation fixed. 0MQ version 2.1.1 (rc1), released on 2011/02/23 =============================================== New functionality ----------------- * New socket option ZMQ_RECONNECT_IVL_MAX added, allows for exponential back-off strategy when reconnecting. * New socket option ZMQ_RECOVERY_IVL_MSEC added, as a fine-grained counterpart to ZMQ_RECOVERY_IVL (for multicast transports). * If memory is exhausted, 0MQ warns with an explicit message before aborting the process. * Size of inproc HWM and SWAP is sum of peers' HWMs and SWAPs (Douglas Greager, Martin Sustrik). Bug fixes --------- * 0MQ no longer asserts in mailbox.cpp when multiple peers connect with the same identity. * 0MQ no longer asserts when rejecting an oversized message. * 0MQ no longer asserts in pipe.cpp when the swap fills up. * zmq_poll now works correctly with an empty poll set. * Many more. Building -------- * 0MQ now builds correctly on CentOS, Debian 6, and SunOS/gcc3. * Added WithOpenPGM configuration into MSVC builds. Known issues ------------ * OpenPGM integration is still not fully stable. 0MQ version 2.1.0 (Beta), released on 2010/12/01 ================================================ New functionality ----------------- * New semantics for zmq_close () and zmq_term () ensure that all messages are sent before the application terminates. This behaviour may be modified using the new ZMQ_LINGER socket option; for further details refer to the reference manual. * The new socket options ZMQ_FD and ZMQ_EVENTS provide a way to integrate 0MQ sockets into existing poll/event loops. * Sockets may now be migrated between OS threads, as long as the application ensures that a full memory barrier is issued. * The 0MQ ABI exported by libzmq.so has been formalised; DSO symbol visibility is used on supported platforms to ensure that only public ABI symbols are exported. The library ABI version has been set to 1.0.0 for this release. * OpenPGM has been updated to version 5.0.92. This version no longer depends on GLIB, and integration with 0MQ should be much improved. * zmq_poll() now honors timeouts precisely, and no longer returns if no events are signaled. * Blocking calls now return EINTR if interrupted by the delivery of a signal; this also means that language bindings which previously had problems with handling SIGINT/^C should now work correctly. * The ZMQ_TYPE socket option was added; this allows retrieval of the socket type after creation. * Added a ZMQ_VERSION macro to zmq.h for compile-time API version detection. * The ZMQ_RECONNECT_IVL and ZMQ_BACKLOG socket options have been added. Bug fixes --------- * Forwarder and streamer devices now handle multi-part messages correctly. * 0MQ no longer asserts when malformed data is received on the wire. * 0MQ internal timers now work correctly if the TSC jumps backwards. * The internal signalling functionality (mailbox) has been improved to automatically resize socket buffers on POSIX systems. * Many more. Building -------- * 0MQ now builds correctly with many more non-GCC compilers (Sun Studio, Intel ICC, CLang). * AIX and HP-UX builds should work now. * FD_SETSIZE has been set to 1024 by default for MSVC builds. * Windows builds using GCC (MinGW) now work out of the box. Distribution ------------ * A simple framework for regression tests has been added, along with a few basic self-tests. The tests can be run using "make check". |
||
obache
|
edf20cda79 |
Import zeromq-2.0.11 as net/zeromq.
The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more. |