- 15 Aug, 2018 1 commit
-
-
Szekely Gyorgy authored
* Add ZMQ_ROUTER_NOTIFY draft socket option
-
- 27 Jul, 2018 1 commit
-
-
Luca Boccassi authored
Solution: move them from DRAFT state to STABLE
-
- 26 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: define and apply parameter naming style: lower_case_
-
- 10 May, 2018 1 commit
-
-
Lionel Flandrin authored
Solution: add a new ZMQ_MULTICAST_LOOP option for UDP sockets.
-
- 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.
-
- 21 Mar, 2018 4 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.
-
Luca Boccassi authored
Solution: bump to 4.2.5
-
- 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");
-
- 05 Mar, 2018 1 commit
-
-
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.
-
- 09 Feb, 2018 2 commits
-
-
Simon Giesecke authored
Solution: add socket option
-
sigiesec authored
Solution: relaxed test assertions, based on the actual time passed, instead of assuming that this equals to the time slept
-
- 08 Feb, 2018 1 commit
-
-
Tetsuya Hayashi authored
-
- 04 Feb, 2018 1 commit
-
-
Luca Boccassi authored
-
- 03 Feb, 2018 1 commit
-
-
Tetsuya Hayashi authored
-
- 02 Feb, 2018 1 commit
-
-
sigiesec authored
Solution: applied clang-format
-
- 13 Dec, 2017 1 commit
-
-
Luca Boccassi authored
Solution: bump changelog, ABI revision, library and packaging version
-
- 16 Nov, 2017 1 commit
-
-
Luca Boccassi authored
Solution: remove it
-
- 25 Oct, 2017 1 commit
-
-
f18m authored
Change ZMQ_THREAD_AFFINITY to ZMQ_THREAD_AFFINITY_CPU_ADD/ZMQ_THREAD_AFFINITY_CPU_REMOVE. Avoid prefix thread names when no prefix was set.
-
- 24 Oct, 2017 1 commit
-
-
Yann Diorcet authored
-
- 17 Oct, 2017 1 commit
-
-
f18m authored
* Add ZMQ_THREAD_NAME_PREFIX ctx option
-
- 16 Oct, 2017 1 commit
-
-
f18m authored
* Background thread scheduling - add ZMQ_THREAD_AFFINITY ctx option; set all thread scheduling options from the context of the secondary thread instead of using the main process thread context! - change ZMQ_THREAD_PRIORITY to support setting NICE of the background thread when using SCHED_OTHER
-
- 09 Oct, 2017 1 commit
-
-
Luca Boccassi authored
Solution: add ZMQ_ZAP_ENFORCE_DOMAIN to hide backward incompatible change and make it disabled by default. In a future release that breaks API compatibility we can then switch the default to enabled in order to achieve full RFC compatibility. Fixes #2762
-
- 19 Sep, 2017 3 commits
- 07 Sep, 2017 3 commits
-
-
Doron Somech authored
-
sigiesec authored
Solution: Renamed, but support querying the property by its old name
-
sigiesec authored
Solution: renamed routing_id fields in pipe_t, renamed ZMQ_CONNECT_RID to ZMQ_CONNECT_ROUTING_ID
-
- 06 Sep, 2017 1 commit
-
-
sigiesec authored
Solution: replace by "routing id"
-
- 01 Sep, 2017 1 commit
-
-
sigiesec authored
Solution: added test case (with dummy implementation of zmq_socket_get_peer_state)
-
- 19 Aug, 2017 1 commit
-
-
Luca Boccassi authored
Solution: move them together with the other DRAFT socket options, and change value of DRAFT ZMQ_BINDTODEVICE from 90 to 92 to avoid clash
-
- 18 Aug, 2017 3 commits
- 16 Aug, 2017 1 commit
-
-
Min RK authored
uint32_t is used in the draft APIs and undefined on MSC 1500 preventing compilation
-
- 04 Aug, 2017 1 commit
-
-
Simon Giesecke authored
Solution: Define them in zmq.h and use them (currently in DRAFT API)
-
- 03 Aug, 2017 1 commit
-
-
Simon Giesecke authored
* Fixing #2002 one way of doing it * Mechanisms can implement a new method `error_detail()` * This error detail have three values for the moment: no_detail (default), protocol, encryption. + generic enough to make sense for all mechanisms. - low granularity level on information. * Fixing #2002: implementation of the error details The ZMQ_EVENT_HANDSHAKE_FAILED event carries the error details as value. * Removed Microsoft extenstion for enum member access This was leading to compilation error under linux. * Adaptation of CURVE test cases * Monitoring event: changed API for detailed events Removed ZMQ_EVENT_HANDSHAKE_FAILED and replaced it by: - ZMQ_EVENT_HANDSHAKE_FAILED_NO_DETAIL, - ZMQ_EVENT_HANDSHAKE_FAILED_PROTOCOL, - ZMQ_EVENT_HANDSHAKE_FAILED_ENCRYPTION Adaptation of text case `security_curve` * Removed event value comparison This was introduced for the previous API model adaptation * Removed the prints in std output and added missing details `current_error_detail` was not set in every protocol error cases * Fixed initialization of current_error_detail * Fixed error in greeting test case The handshake failure due to mechanism mismatch in greeting is actually a protocol error. The error handling method consider it like so and send a protocol handshake failure monitoring event instead of no_detail. Fixed the test_security_curve expectation as well. * Upgraded tests of monitoring events The tests check the number of monitoring events received * Problem: does not build under Linux or without ZMQ_DRAFT_API Solution: - properly use ZMQ_DRAFT_API conditional compilation - use receive timeouts instead of Sleep * Problem: duplicate definition of variable 'timeout' Solution: merged definitions * Problem: inconsistent timing dependencies Solution: reduce timing dependency by using timeouts at more places * Problem: assertion failure under Linux due to unexpected monitor event Solution: output event type to aid debugging * Problem: erroneous assertion code * Problem: assertion failure with a garbage server key due to an extra third event Solution: changed assertion to expect three events (needs to be checked) * Problem: extra include directive to non-existent file Solution: removed include directive * Problem: assertion failure on appveyor for unknown reason Solution: improve debug output * Problem: no build with libsodium and draft api Solution: add build configurations with libsodium and draft api * Problem: assertion failure on CI Solution: change assertion to reflect actual behaviour on CI (at least temporarily) * Problem: error in condition in assertion code * Problem: assertion failure on CI Solution: generalize assertion to match behavior on CI * Problem: assertion failures on CI Solution: removed inconsistent assertion on no monitor events before flushing improved debuggability by converting function into macro * Problem: diverging test code for three analogous test cases with garbage key Solution: extract common code into function * Problem: does not build without ZMQ_BUILD_DRAFT_API Solution: introduce dummy variable * Attempt to remove workaround regarding ZMQ_EVENT_HANDSHAKE_FAILED_NO_DETAIL again * Problem: EAGAIN error after handshake complete if there is no more data in inbuffer Solution: Skip tcp_read attempt in that case * Problem: handshaking event emitted after handshaking failed Solution: use stream_engine_t::handshaking instead of mechanism_t::status() to determine whether still handshaking * Include error code in debug output * Improve debugging output: output flushed events * Split up ZMQ_EVENT_HANDSHAKE_FAILED_PROTOCOL into ZMQ_EVENT_HANDSHAKE_FAILED_ZMTP and ZMQ_EVENT_HANDSHAKE_FAILED_ZAP * Fixed compilation without ZMQ_BUILD_DRAFT_API * Renamed ZMQ_EVENT_HANDSHAKE_SUCCEED to ZMQ_EVENT_HANDSHAKE_SUCCEEDED for language consistency * Renamed ZMQ_EVENT_HANDSHAKE_SUCCEED to ZMQ_EVENT_HANDSHAKE_SUCCEEDED for language consistency * Renamed ZMQ_EVENT_HANDSHAKE_SUCCEED to ZMQ_EVENT_HANDSHAKE_SUCCEEDED for language consistency * Fixed assert_monitor_event (require event instead of allowing no event) Reverted erroneous change to handshaking condition Renamed test_wrong_key to test_garbage_key Generalized assumption in test_garbage_key to allow for ZMQ_EVENT_HANDSHAKE_FAILED_NO_DETAIL with error == EPIPE * Better isolate test cases from each other by providing a fresh context & server for each * Added diagnostic output * Changed assertion to reflect actual behavior on CI * Fixed formatting, observe maximum line length * Fixed formatting, observe maximum line length * Increase timeout to check if this fixes valgrind run * Close server with close_zero_linger * Increase timeout to check if this fixes valgrind run * Increase timeout to check if this fixes valgrind run * Generalize assertion to also work with valgrind * Fixed formatting * Add more diagnostic output * Generalize assertion to also work with valgrind
-