- 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
-
- 08 Nov, 2014 1 commit
-
-
J.T. Conklin authored
-
- 12 Aug, 2014 1 commit
-
-
Pieter Hintjens authored
Solution: change setsockopts on printable keys to expect 41, nor 40 bytes. Code still accepts 40 bytes for compatibility, and copies the key to a well-terminated string before using it. Fixes #1148
-
- 20 Jun, 2014 1 commit
-
-
Mike Gatny authored
-
- 12 May, 2014 1 commit
-
-
Stoian Ivanov authored
-
- 09 May, 2014 1 commit
-
-
Will Strang authored
-
- 01 Jan, 2014 2 commits
-
-
Pieter Hintjens authored
- This seems redundant; is there a use case for NOT providing the IPC credentials to the ZAP authenticator? - More, why is IPC authentication done via libzmq instead of ZAP? Is it because we're missing the transport type on the ZAP request?
-
Pieter Hintjens authored
- put into alphabetical order - there was no consistency in previous ordering
-
- 06 Dec, 2013 1 commit
-
-
Brandon Carpenter authored
Another take on LIBZMQ-568 to allow filtering IPC connections, this time using ZAP. This change is backward compatible. If the ZMQ_ZAP_IPC_CREDS option is set, the user, group, and process IDs of the peer process are appended to the address (separated by colons) of a ZAP request; otherwise, nothing changes. See LIBZMQ-568 and zmq_setsockopt documentation for more information.
-
- 25 Nov, 2013 1 commit
-
-
Chris Laws authored
-
- 09 Oct, 2013 1 commit
-
-
Pieter Hintjens authored
-
- 20 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
* ZMQ_REQ_STRICT was negative option (default 1) which goes against the standard, where defaults are zero. I renamed this to ZMQ_REQ_RELAXED. * ZMQ_REQ_REQUEST_IDS felt clumsy and describes the technical solution rather than the problem/requirement. I changed to ZMQ_REQ_CORRELATE which seems more explicit.
-
- 12 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
On ZMQ_CURVE_xxxKEY fetches, would return 41 bytes into caller's 40-byte buffer. Now these fetches only return 41 bytes if the caller explicitly provides a 41-byte buffer (i.e. the option size is 41).
-