- 21 Apr, 2017 1 commit
-
-
Jim Garlick authored
Problem: principals are looked up unconditionally with the GSS_C_NT_HOSTBASED_SERVICE name type. Solution: Add two new socket options to set the name type for ZMQ_GSSAPI_PRINCIPAL and ZMQ_GSSAPI_SERVICE_PRINCIPAL: ZMQ_GSSAPI_PRINCIPAL_NAMETYPE ZMQ_GSSAPI_SERVICE_PRINCIPAL_NAMETYPE They take an integer argument which must be one of ZMQ_GSSAPI_NT_HOSTBASED (0) - default ZMQ_GSSAPI_NT_USER_NAME (1) ZMQ_GSSAPI_NT_KRB5_PRINCIPAL (2) These correspond to GSSAPI name types of: GSS_C_NT_HOSTBASED_SERVICE GSS_C_NT_USER_NAME GSS_KRB5_NT_PRINCIPAL_NAME Fixes #2542
-
- 26 Mar, 2017 1 commit
-
-
evoskuil authored
-
- 11 Mar, 2017 1 commit
-
-
somdoron authored
solution: deprecate zmq_poll in favor of zmq_poller
-
- 18 Feb, 2017 1 commit
-
-
Luca Boccassi authored
Solution: bump changelog, ABI revision, library and packaging version
-
- 31 Dec, 2016 1 commit
-
-
Luca Boccassi authored
Solution: add new changelog entry, bump library version in zmq.h and bump ABI version in configure.ac and CMakeLists.txt
-
- 30 Dec, 2016 2 commits
-
-
Vincent Tellier authored
- Moved new events in draft section + added to zmq_draft.h - Removed the remainning tabs - Reverted the hard error (back to soft error) in curve_server.cpp => The feature doesn't works anymore
-
Vincent Tellier authored
Added two new monitoring events: - ZMQ_EVENT_HANDSHAKE_SUCCEED is raised once the encryption handshake succeed - ZMQ_EVENT_HANDSHAKE_FAILED is raised when it failed Both events are raised on server and client side.
-
- 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
-
- 05 Dec, 2016 1 commit
-
-
Luca Boccassi authored
Solution: restore inclusion of poll.h if using poll before zmq.h as it was originally, as AIX redefines the POSIX structures and provides compatibility macros. Also add alternative aliases for 32 bit AIX's pollitem struct: events -> reqevents revents -> rtnevents
-
- 20 Nov, 2016 1 commit
-
-
Luca Boccassi authored
Solution: add a ZMQ_MSG_T_SIZE context read-only option so that wrappers can call zmq_ctx_get (ctx, ZMQ_MSG_T_SIZE) to get the size at runtime.
-
- 08 Nov, 2016 1 commit
-
-
Luca Boccassi authored
Solution: update NEWS, include/zmq.h and packaging
-
- 01 Nov, 2016 1 commit
-
-
Luca Boccassi authored
Solution: move comment further below to declare new socket options as stable for the 4.2.0 release.
-
- 28 Oct, 2016 2 commits
-
-
Luca Boccassi authored
Solution: try to detect architecture if building with VC++ and hardcode pointer size accordingly. Expressions are not allowed inside declspec intrinsics, which includes other intrinsics.
-
Luca Boccassi authored
Solution: use compiler's alignment attributes instead which is clearer and less of a hack. Pointer alignment violations causing crashes on architectures such as sparc64 and aarch64. This also avoid triggering ABI checkers as the change is compatible even though applications that suffer from the bug should rebuild to take advantage of the fix.
-
- 27 Sep, 2016 2 commits
-
-
Min RK authored
avoids unnecessary heap allocations, races on the number of items
-
Min RK authored
Solution: zmq_poller_wait_all signals all events allows signaling multiple events with one call to zmq_poller_wait_all rather than emitting only one event. this prepares for zmq_poll being based on zmq_poller, which requires events for all sockets rather than just one.
-
- 01 Jun, 2016 1 commit
-
-
Yann Diorcet authored
-
- 19 May, 2016 1 commit
-
-
evoskuil authored
-
- 15 May, 2016 1 commit
-
-
Bitiquinho authored
-
- 04 May, 2016 2 commits
-
-
hitstergtd authored
Solution: As preparation for 4.2 release, move the zmq_sendiov and zmq_recviov API methods under the Deprecated Methods section. Note: the actual methods have NOT been deprecated yet, functionally speaking however it is good to let API users know early. Moreover, these methods were not ever considered stable, at least according to src/zmq.h, and have no associated man pages.
-
Doron Somech authored
-
- 03 May, 2016 1 commit
-
-
Doron Somech authored
-
- 02 May, 2016 6 commits
-
-
Luca Boccassi authored
Solution: mark them as DRAFT APIs
-
Luca Boccassi authored
Solution: mark them as DRAFT APIs
-
Luca Boccassi authored
Solution: mark them as DRAFT APIs
-
Luca Boccassi authored
Solution: mark them as DRAFT APIs
-
Luca Boccassi authored
Solution: mark them as DRAFT APIs
-
Luca Boccassi authored
Solution: add support for --enable-drafts/ENABLE_DRAFTS=ON in Autools and CMake.
-
- 01 May, 2016 1 commit
-
-
hitstergtd authored
Solution: Fix it and align with the documentation; zmq_socket_monitor(3) outlines that ZMQ socket monitoring is supported for TCP, IPC and TIPC.
-
- 25 Apr, 2016 1 commit
-
-
hitstergtd authored
Solution: fix them
-
- 24 Apr, 2016 1 commit
-
-
somdoron authored
-
- 21 Apr, 2016 1 commit
-
-
somdoron authored
-
- 05 Apr, 2016 1 commit
-
-
Jim Klimov authored
Problem: Recent deprecation of the "zmq_utils.h" header file caused pedantic compilations (including czmq) to fail because non-portable #warning is used. Solution: Limit the deprecation warnings to compilers known or assumed to support the "#pragma message" (GCC, MSVC, CLANG) and wrap with GCC directives to not treat these warnings as errors on paranoid builds.
-
- 29 Mar, 2016 1 commit
-
-
Geof Nieboer authored
Previous change broke MSVC b/c MSVC doesn't support #warning
-
- 11 Mar, 2016 1 commit
-
-
Ben Gray authored
-
- 18 Feb, 2016 1 commit
-
-
Min RK authored
instead of removing it, which breaks downstream builds.
-
- 09 Feb, 2016 4 commits
-
-
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.
-
Pieter Hintjens authored
These options are confusing and redundant. Their names suggest they apply to the tcp:// transport, yet they are used for all stream protocols. The methods zmq::set_tcp_receive_buffer and zmq::set_tcp_send_buffer don't use these values at all, they use ZMQ_SNDBUF and ZMQ_RCVBUF. Solution: merge these new options into ZMQ_SNDBUF and ZMQ_RCVBUF. This means defaulting these two options to 8192, and removing the new options. We now have ZMQ_SNDBUF and ZMQ_RCVBUF being used both for TCP socket control, and for input/output buffering. Note: the default for SNDBUF and RCVBUF are otherwise 4096.
-
Pieter Hintjens authored
This option has a few issues. The name is long and clumsy. The functonality is not smooth: one must set both this and ZMQ_XPUB_VERBOSE at the same time, or things will break mysteriously. Solution: rename to ZMQ_XPUB_VERBOSER and make an atomic option. That is, implicitly does ZMQ_XPUB_VERBOSE.
-
Pieter Hintjens authored
Solution: rename to ZMQ_MAXRT This is the option name used on Windows, so easier to use and remember.
-