- 02 Feb, 2019 1 commit
-
-
Simon Giesecke authored
Solution: add monitor event socket option
-
- 15 Aug, 2018 2 commits
-
-
Simon Giesecke authored
Solution: extract functionality into get_effective_conflate_option
-
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
-
- 26 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: define and apply parameter naming style: lower_case_
-
- 22 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: removed
-
- 18 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: change options_t.type to int8_t
-
- 13 May, 2018 1 commit
-
-
Luca Boccassi authored
Solution: add missing const qualifier to internal functions
-
- 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");
-
- 06 Mar, 2018 1 commit
-
-
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
-
- 18 Oct, 2017 1 commit
-
-
sigiesec authored
Solution: add "milliseconds"
-
- 09 Oct, 2017 2 commits
-
-
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
-
Luca Boccassi authored
Solution: remove unused zap_ipc_creds boolean variable
-
- 19 Sep, 2017 2 commits
- 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 1 commit
-
-
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
-
- 14 May, 2016 1 commit
-
-
evoskuil authored
-
- 28 Feb, 2016 1 commit
-
-
Steven Chamberlain authored
Platforms that have struct ucred, typically declare it in sys/ucred.h
-
- 09 Feb, 2016 3 commits
-
-
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
Solution: rename to ZMQ_MAXRT This is the option name used on Windows, so easier to use and remember.
-
Luca Boccassi authored
Solution: rename socket option (and variables and files) from usefd to use_fd.
-
- 08 Feb, 2016 1 commit
-
-
Luca Boccassi authored
Solution: rename socket option (and variables and files) from pre_allocated_fd to usefd.
-
- 04 Feb, 2016 1 commit
-
-
Luca Boccassi authored
Solution: add new [set|get]sockopt ZMQ_PRE_ALLOCATED_FD to allow users to let ZMQ use a pre-allocated file descriptor instead of allocating a new one. Update [set|get]sockopt documentation and test accordingly. The main use case for this feature is a socket-activated systemd service. For more information about this feature see: http://0pointer.de/blog/projects/socket-activation.html
-
- 28 Jan, 2016 1 commit
-
-
Constantin Rack authored
Solution: update to 2016
-
- 08 Dec, 2015 1 commit
-
-
Ilya Kulakov authored
VMCI transport allows fast communication between the Host and a virtual machine, between virtual machines on the same host, and within a virtual machine (like IPC). It requires VMware to be installed on the host and Guest Additions to be installed on a guest.
-
- 23 Nov, 2015 1 commit
-
-
Jim Hague authored
Fixes #1646
-
- 13 Nov, 2015 1 commit
-
-
Constantin Rack authored
Solution: make tcp_recv_buffer_size and tcp_send_buffer_size unsigned
-