- 13 May, 2018 5 commits
-
-
Lionel Flandrin authored
Solution: if a binding interface is provided in the sender URL we pass it to IP[V6]_MULTICAST_IF setsockopt
-
Luca Boccassi authored
Solution: add missing const qualifier to internal functions
-
Luca Boccassi authored
Solution: do it explicitly to fix build on Solaris 10/11 with the Sun compiler
-
Simon Giesecke authored
Solution: remove constness on pair arguments. Fixes #3090
-
Simon Giesecke authored
Solution: use proper types
-
- 10 May, 2018 1 commit
-
-
Lionel Flandrin authored
Solution: add a new ZMQ_MULTICAST_LOOP option for UDP sockets.
-
- 09 May, 2018 1 commit
-
-
Lionel Flandrin authored
Solution: Add IPv6 support
-
- 04 May, 2018 2 commits
-
-
Lionel Flandrin authored
for multicast Solution: augment the UDP URL syntax to accept an interface specifier with a syntax similar to the PGM urls. Fixes #2212
-
Lionel Flandrin authored
Solution: factor the code into ip_resolver, add IPv6 support and unit tests.
-
- 03 May, 2018 2 commits
-
-
Lionel Flandrin authored
Solution: replace it with the ip_resolver code shared with the TCP address code It simplifies the UDP parsing code and makes it behave more like the TCP counterpart, in particular it's not possible to connect to hosts by name and bind by NIC names. It also adds support for "*" port resolving to 0 (useful to let the OS allocate the port number).
-
Lionel Flandrin authored
Solution: return an error in this situation but still allow using an explicit "0" if somebody really wants to connect to port 0. This shouldn't break any existing code because a "*" port was already rejected in an early test in the TCP path in zmq::socket_base_t::connect.
-
- 02 May, 2018 1 commit
-
-
Lionel Flandrin authored
Solution: Factor the code into a different file with a well defined API and add unit tests.
-
- 28 Apr, 2018 1 commit
-
-
Luca Boccassi authored
Solution: ignore command messages in the REQ session to avoid disrupting the state machine. Commands are handled by the engine before handing off to the session.
-
- 19 Apr, 2018 1 commit
-
-
Maks Naumov authored
event_accepted() already accepts fd_t type and there is no reason to cast it to int type Moreover, on Windows x64 this leads to truncation memsize -> int
-
- 13 Apr, 2018 1 commit
-
-
asafkahlon authored
* Implement the wsa_error_no function with switch-case Signed-off-by:
Asaf Kahlon <asafka7@gmail.com>
-
- 03 Apr, 2018 1 commit
-
- 02 Apr, 2018 1 commit
-
-
Luca Boccassi authored
Solution: change comments Fixes: #3036
-
- 28 Mar, 2018 1 commit
-
-
Simon Giesecke authored
Solution: do not call getsockopt to query thread-safety of a socket
-
- 23 Mar, 2018 2 commits
-
-
Luca Boccassi authored
Solution: revert the revert! Revert "Problem: regression in 4.2.3 went unnoticed, want to release 4.2.5" This reverts commit 5f17e26f.
-
Luca Boccassi authored
Solution: revert DRAFT -> STABLE API transition so that we can do a bugfix-only 4.2.5 release. Will be re-reverted once tagged. Revert "Problem: ZMQ_BINDTODEVICE has met STABLE conditions" This reverts commit 3cb79f50. Revert "Problem: ZMQ_MSG_GSSAPI_* have met STABLE conditions" This reverts commit 374da420. Revert "Problem: ZMQ_MSG_T_SIZE has met STABLE conditions" This reverts commit 6411c4a2. Revert "Problem: docs say STABLE API still in DRAFT" This reverts commit 9f2f30b7.
-
- 22 Mar, 2018 1 commit
-
-
Luca Boccassi authored
Solution: like for other mechanism, do not enforce strict ZAP protocol adherence unless the specific socket option is enabled with NULL auth. Add test to exercise this functionality, and fix ZAP test to set the socket option when it uses NULL auth. See: https://github.com/zeromq/pyzmq/pull/1152
-
- 21 Mar, 2018 3 commits
-
-
Luca Boccassi authored
Solution: move them from DRAFT to STABLE since it's been in a public release, committed for 6+ months and has not changed.
-
Luca Boccassi authored
Solution: move them from DRAFT to STABLE since it's been in a public release, committed for 6+ months and has not changed.
-
Luca Boccassi authored
Solution: move it from DRAFT to STABLE since it's been in a public release, committed for 6+ months and has not changed. Given a new STABLE symbol has been added, bump minor version number.
-
- 20 Mar, 2018 1 commit
-
-
Pontus Sköldström authored
-
- 19 Mar, 2018 2 commits
-
-
Pontus Sköldström authored
-
Luca Boccassi authored
Solution: restrict it only to the original issue #2632, Tweetnacl on *NIX when using /dev/urandom, ie: without the new Linux getrandom() syscall. Existing applications might use atexit to register cleanup functions (like CZMQ does), and the current change as-is imposes an ordering that did not exist before - the context MUST be created BEFORE registering the cleanup with atexit. This is a backward incompatible change that is reported to cause aborts in some applications. Although libsodium's documentation says that its initialisation APIs is not thread-safe, nobody has ever reported an issue with it, so avoiding the global init/deinit in the libsodium case is the less risky option we have. Tweetnacl users on Windows and on Linux with getrandom (glibc 2.25 and Linux kernel 3.17) are not affected by the original issue. Fixes #2991
-
- 14 Mar, 2018 1 commit
-
-
Pontus Sköldström authored
Lets the application set per-connection metadata. Metadata is specified as "X-key:value" and set using zmq_setsockopt, eg: zmq_setsockopt (s, ZMQ_METADATA, "X-key:value", 11); The peer can then obtain the metadata from a received message: char *data = zmq_msg_gets(msg, "X-key");
-
- 12 Mar, 2018 1 commit
-
-
Sergey Kachanovskiy authored
* Fixes issue 2963, ref stream_engine.cpp:981 * Fixes issue 2963, ref socks_connecter.cpp:158 * Fixes issue 2963, ref tcp_listener.cpp:144 * Fixes issue 2963, ref tcp_connecter.cpp:423 * Fixes issue 2963, ref socks_connecter.cpp:436 * Fixes issue 2963, ref tcp_listener.cpp:179 * Fixes issue 2963, ref tcp_listener.cpp:268 * Fixes issue 2963, ref tcp_connecter.cpp:160
-
- 10 Mar, 2018 3 commits
-
-
Luca Boccassi authored
Solution: commit clang-format-diff
-
Luca Boccassi authored
Solution: add pragma to make clang-format ignore the external code
-
Manuel Segura authored
* Problem: Still need to port over more files to VxWorks 6.x Solution: Port more files to VxWorks 6.x * Problem: Need to port over remaining files to VxWorks 6.x. Also remove POSIX thread dependency for VxWorks (because of priority inversion problem in POSIX mutexes with VxWorks 6.x processes) Solution: Port over remaining files to VxWorks 6.x. Also removed POSIX thread dependency for VxWorks * Problem: Needed to modify TCP, UDP, TIPC classes with #ifdefs to be compatible with VxWorks 6.x. Solution: Modify TCP, UDP, TIPC classes with #ifdefs to be compatible with VxWorks 6.x
-
- 09 Mar, 2018 1 commit
-
-
Kachanovskiy authored
-
- 07 Mar, 2018 2 commits
-
-
Pontus.Skoeldstroem authored
* Tests for different TIPC address types and code cleanup * Adds tests for binding/connecting with different TIPC address types using Unity * Adds error checking for address type misuse
-
Simon Giesecke authored
-
- 06 Mar, 2018 3 commits
-
-
Luca Boccassi authored
Solution: do not rely __cplusplus >= 201103L to detect whether the compiler supports thread safe static initialisation, but check only the proper feature preprocessor macro. GCC introduced it in version 8, and Clang in version 6.
-
Luca Boccassi authored
Solution: initialise variable in options.cpp to dummy value to fix compiler complaint: src/options.cpp: In function 'int zmq::do_setsockopt_int_as_bool_strict(const void*, size_t, bool*)': src/options.cpp:121:5: error: 'value' may be used uninitialized in this function [-Werror=maybe-uninitialized] src/options.cpp: In function 'int zmq::do_setsockopt_int_as_bool_relaxed(const void*, size_t, bool*)': src/options.cpp:135:31: error: 'value' may be used uninitialized in this function [-Werror=maybe-uninitialized]
-
Simon Giesecke authored
Solution: extracted common code into do_getsockopt/do_setsockopt functions
-
- 05 Mar, 2018 2 commits
-
-
Luca Boccassi authored
Solution: run make clang-format-diff and commit the changes.
-
Stefan Kaes authored
The zero copy decoding strategy implemented for 4.2.0 can lead to a large increase of main memory usage in some cases (I have seen one program go up to 40G from 10G after upgrading from 4.1.4). This commit adds a new option to contexts, called ZMQ_ZERO_COPY_RECV, which allows one to switch to the old decoding strategy.
-