- 15 Aug, 2018 1 commit
-
-
Szekely Gyorgy authored
* Add ZMQ_ROUTER_NOTIFY draft socket option
-
- 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 1 commit
-
-
Luca Boccassi authored
Solution: update them
-
- 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: Replaced by "routing id"
-
sigiesec authored
Solution: change docs to refer to "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.
-
- 24 Apr, 2017 1 commit
-
-
Jim Garlick authored
Problem: GSSAPI NAMETYPE options were not documented in man pages for zmq_getsockopt() and zmq_setsockopt(). Solution: add new options to these manual pages.
-
- 26 Dec, 2016 1 commit
-
-
Luca Boccassi authored
Solution: add paragraphs to zmq_get/setsockopt man pages
-
- 21 Sep, 2016 1 commit
-
-
Patrik Wenger authored
The effect can be seen on http://api.zeromq.org/4-2:zmq-getsockopt at options ZMQ_USE_FD and ZMQ_RATE. Solution: fix length of squiggly line under option title
-
- 09 Feb, 2016 4 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
The proper name is ZMQ_THREAD_SAFE Solution: fix in the documentation.
-
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
-
- 01 Feb, 2016 3 commits
-
-
Pieter Hintjens authored
-
Pieter Hintjens authored
-
Constantin Rack authored
Solution: Replace with `zmq_ctx_term`
-
- 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 2 commits
-
-
Constantin Rack authored
Solution: fix documentation
-
Constantin Rack authored
Solution: change option behaviour and adopt documentation
-
- 08 Nov, 2015 1 commit
-
-
Jens Auer authored
-
- 08 Oct, 2015 1 commit
-
-
Jens Auer authored
-
- 13 Sep, 2015 1 commit
-
-
Pieter Hintjens authored
- both are thread safe - they do not accept ZMQ_SNDMORE nor ZMQ_RCVMORE
-
- 11 Sep, 2015 1 commit
-
-
Pieter Hintjens authored
Solution: add man pages/sections for: * ZMQ_SERVER * ZMQ_CLIENT * ZMQ_THREADSAFE * zmq_msg_routing_id * zmq_msg_set_routing_id
-
- 06 Aug, 2015 1 commit
-
-
KIU Shueng Chuan authored
-
- 04 Aug, 2015 2 commits
-
-
KIU Shueng Chuan authored
-
KIU Shueng Chuan authored
was fixed in zmq_setsockopt.txt but not in zmq_getsockopt.txt
-
- 08 Jul, 2015 2 commits
-
-
Juha Reunanen authored
-
Juha Reunanen authored
-
- 26 Jan, 2015 1 commit
-
-
Julien Ruffin authored
ZMQ_INVERT_MATCHING reverses the PUB/SUB prefix matching. The subscription list becomes a rejection list. The PUB socket sends messages to all connected (X)SUB sockets that do not have any matching subscription. Whenever the option is used on a PUB/XPUB socket, any connecting SUB sockets must also set it or they will reject everything the publisher sends them. XSUB sockets are unaffected because they do not filter out incoming messages.
-
- 09 Jan, 2015 1 commit
-
-
Thomas Rodgers authored
-