- 27 Jun, 2019 1 commit
-
-
jean-airoldie authored
Solution: Added a socket option to configure them at runtime.
-
- 11 Jun, 2019 1 commit
-
-
Luca Boccassi authored
Solution: apply clang-format-diff
-
- 10 Jun, 2019 1 commit
-
-
Christophe Guillon authored
-
- 18 May, 2019 1 commit
-
-
Luca Boccassi authored
Solution: now that clang-format 6+ is used in the CI, fix it
-
- 02 Feb, 2019 1 commit
-
-
Simon Giesecke authored
Solution: add monitor event socket option
-
- 15 Aug, 2018 1 commit
-
-
Szekely Gyorgy authored
* Add ZMQ_ROUTER_NOTIFY draft socket option
-
- 30 May, 2018 1 commit
-
-
Simon Giesecke authored
Problem: code style issues in options_t (C-style cast, suboptimal std::string::find call, redundant method is_valid) Solution: resolved these issues
-
- 28 May, 2018 2 commits
-
-
Simon Giesecke authored
Solution: replace by reinterpret_casts or avoid entirely
-
Simon Giesecke authored
Solution: use UCHAR_MAX constant instead
-
- 26 May, 2018 3 commits
-
-
Simon Giesecke authored
Solution: remove else
-
Simon Giesecke authored
Solution: replace by bool literals
-
Simon Giesecke authored
Solution: define and apply parameter naming style: lower_case_
-
- 25 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: use UINT16_MAX
-
- 22 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: removed
-
- 18 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: replace by C++-style casts
-
- 10 May, 2018 1 commit
-
-
Lionel Flandrin authored
Solution: add a new ZMQ_MULTICAST_LOOP option for UDP sockets.
-
- 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");
-
- 10 Mar, 2018 2 commits
-
-
Luca Boccassi authored
Solution: commit clang-format-diff
-
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
-
- 06 Mar, 2018 2 commits
-
-
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 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 1 commit
-
-
Simon Giesecke authored
Solution: add socket option
-
- 08 Feb, 2018 1 commit
-
-
Simon Giesecke authored
* Problem: race conditions for options.linger Solution: make options.linger atomic
-
- 02 Feb, 2018 1 commit
-
-
sigiesec authored
Solution: applied clang-format
-
- 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 1 commit
-
-
sigiesec authored
Solution: replace by "routing id"
-
- 07 Sep, 2017 1 commit
-
-
Doron Somech authored
-
- 06 Sep, 2017 1 commit
-
-
sigiesec authored
Solution: replace by "routing id"
-
- 31 Jul, 2017 1 commit
-
-
Brian Russell authored
Linux now supports Virtual Routing and Forwarding (VRF) as per: https://www.kernel.org/doc/Documentation/networking/vrf.txt In order for an application to bind or connect to a socket with an address in a VRF, they need to first bind the socket to the VRF device: setsockopt(sd, SOL_SOCKET, SO_BINDTODEVICE, dev, strlen(dev)+1); Note "dev" is the VRF device, eg. VRF "blue", rather than an interface enslaved to the VRF. Add a new socket option, ZMQ_BINDTODEVICE, to bind a socket to a device. In general, if a socket is bound to a device, eg. an interface, only packets received from that particular device are processed by the socket. If device is a VRF device, then subsequent binds/connects to that socket use addresses in the VRF routing table.
-
- 25 Apr, 2017 1 commit
-
-
Jim Garlick authored
Problem: GSSAPI DRAFT code was made conditional on ZMQ_BUILD_DRAFT_API, but zmq_draft.h duplicates the DRAFT symbols definitions from zmq.h so this is unnecessary. Solution: drop the extra ifdefs
-
- 24 Apr, 2017 2 commits
-
-
Jim Garlick authored
Problem: GSSAPI NAMETYPE options were added to zmq_setsockopt() but not zmq_getsockopt(). Add them to zmq_getsockopt().
-
Jim Garlick authored
Problem: The new GSSAPI NAMESPACE options should have been added to the DRAFT section of the API so they can be changed until stabilized. Solution: - Move defines to the DRAFT section of zmq.h - Duplicate them in zmq_draft.h, as is the local custom - Compile only if defined (ZMQ_BUILD_DRAFT_API) - Refactor internals slightly to avoid #ifdef hell
-
- 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
-
- 19 Dec, 2016 1 commit
-
-
Wojciech Kula authored
Solution: set_curve_key method in options_t struct with little improvement in switch-case block
-
- 16 Dec, 2016 2 commits
-
-
Luca Boccassi authored
Solution: Revert "Problem: Duplicated code" This reverts commit 022eeaf3.
-
Wojciech Kula authored
Solution: set_curve_key method in options_t struct with little improvement in switch-case block
-
- 03 May, 2016 1 commit
-
-
somdoron authored
-
- 18 Feb, 2016 1 commit
-
-
Osiris authored
Solution: Phase I - make precompiled.hpp be first file included in every source file
-
- 16 Feb, 2016 1 commit
-
-
Luca Boccassi authored
Solution: always initialised zmq::options_t class variables arrays to avoid reading uninitialised data when CURVE is not yet configured and a getsockopt ZMQ_CURVE_{SERVER | PUBLIC | SECRET]KEY is issued.
-