- 04 Feb, 2020 1 commit
-
-
Gudmundur Adalsteinsson authored
Solution: Fix typo
-
- 15 Jan, 2019 1 commit
-
-
Luca Boccassi authored
Solution: remove documents and tests for ZMQ_THREAD_PRIORITY getter. It never worked and can never work as it has the same value as a get-only option ZMQ_SOCKET_LIMIT. It cannot be changed without breaking ABI. Note that the setter works fine as ZMQ_SOCKET_LIMIT is get-only.
-
- 18 Nov, 2018 1 commit
-
-
Luca Boccassi authored
Solution: add one so that class-based bindings can easily use them
-
- 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 2 commits
-
-
Luca Boccassi authored
Solution: update manpages
-
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.
-
- 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.
-
- 29 Dec, 2016 1 commit
-
-
Luca Boccassi authored
Solution: move it there, add it to src/zmq_draft.h and clarify in the documentation and in the NEWS file that this option is not yet stable
-
- 20 Nov, 2016 1 commit
-
-
Luca Boccassi authored
Solution: mention it in zmq_ctx_get manpage
-
- 09 Feb, 2016 1 commit
-
-
Pieter Hintjens authored
And I'm on a reasonably sized laptop. I think allocating INT_MAX memory is dangerous in a test case. Solution: expose this as a context option. I've used ZMQ_MAX_MSGSZ and documented it and implemented the API. However I don't know how to get the parent context for a socket, so the code in zmq.cpp is still unfinished.
-
- 17 Nov, 2014 1 commit
-
-
Pieter Hintjens authored
Solution: set defaults back to infinity, and add new context option, ZMQ_BLOCKY that the user can set to false to get a less surprising behavior on context termination. Eg. zmq_ctx_set (ctx, ZMQ_BLOCKY, false);
-
- 14 Feb, 2014 1 commit
-
-
Olaf Mandel authored
As per suggestion by Pieter Hintjens. Also update wording in zmq_ctx_set manual a bit.
-
- 13 Feb, 2014 1 commit
-
-
Olaf Mandel authored
The new options allows querying the maximum allowed number of sockets. This is system dependent and cannot be encoded in the include file as a preprocessor macro: for ZMQ_USE_SELECT, this depends on the FD_SETSIZE macro at time of library compilation, not at time of include file use.
-
- 02 Oct, 2013 1 commit
-
-
Dylan Cali authored
-
- 15 Apr, 2013 1 commit
-
-
Pieter Hintjens authored
contributors and doesn't reflect the real process. I've taken out all named authors and referred to the contribution policy. Hopefully this will improve the contributions to the man pages.
-
- 31 Jan, 2013 1 commit
-
-
Pieter Hintjens authored
-
- 20 Mar, 2012 1 commit
-
-
Pieter Hintjens authored
* Implemented new ctx API (_new, _destroy, _get, _set) * Removed 'typesafe' macros from zmq.h * Added support for MAX_SOCKETS (was tied into change for #337) * Created new man pages
-