- 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
-
- 08 Nov, 2015 1 commit
-
-
Jens Auer authored
-
- 08 Oct, 2015 1 commit
-
-
Jens Auer authored
-
- 06 Sep, 2015 1 commit
-
-
Constantin Rack authored
-
- 06 Aug, 2015 1 commit
-
-
KIU Shueng Chuan authored
-
- 04 Aug, 2015 1 commit
-
-
KIU Shueng Chuan authored
-
- 24 Jun, 2015 1 commit
-
-
Jonathan Reams authored
This commit adds ZMTP connection heartbeats described in http://rfc.zeromq.org/spec:37/ZMTP.
-
- 05 Jun, 2015 1 commit
-
-
Richard Newton authored
-
- 02 Jun, 2015 1 commit
-
-
Pieter Hintjens authored
Of course people still "can" distributed the sources under the LGPLv3. However we provide COPYING.LESSER with additional grants. Solution: specify these grants in the header of each source file.
-
- 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.
-
- 23 Jan, 2015 1 commit
-
-
Pieter Hintjens authored
Symptom is that ZMQ_STREAM sockets in 4.1.0 and 4.1.1 generate zero sized messages on each new connection, unlike 4.0.x which did not do this. Person who made this commit also changed test cases so that contract breakage did not show. Same person was later banned for persistently poor form in CZMQ contributions. Solution: enable connect notifications on ZMQ_STREAM sockets using a new ZMQ_STREAM_NOTIFY setting. By default, socket does not deliver notifications, and behaves as in 4.0.x. Fixes #1316
-
- 22 Jan, 2015 1 commit
-
-
Pieter Hintjens authored
Solution: update for 2015 Fixes #1320
-
- 12 Aug, 2014 1 commit
-
-
Martin Hurton authored
-
- 08 Aug, 2014 2 commits
-
-
kreuzberger authored
-
kreuzberger authored
-
- 22 Jun, 2014 1 commit
-
-
Martin Hurton authored
This is still raw and experimental. To connect through a SOCKS proxy, set ZMQ_SOCKS_PROXY socket option on socket before issuing a connect call, e.g.: zmq_setsockopt (s, ZMQ_SOCKS_PROXY, "127.0.0.1:22222", strlen ("127.0.0.1:22222")); zmq_connect (s, "tcp://127.0.0.1:5555"); Known limitations: - only SOCKS version 5 supported - authentication not supported - new option is still undocumented
-
- 09 May, 2014 1 commit
-
-
Will Strang authored
-
- 24 Apr, 2014 3 commits
-
-
Chris Busbey authored
-
Chris Busbey authored
-
Chris Busbey authored
-
- 02 Jan, 2014 1 commit
-
-
Pieter Hintjens authored
-
- 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.
-
- 04 Dec, 2013 1 commit
-
-
Brandon Carpenter authored
Adds sets of process (Linux only), user, and group IDs for filtering connections from peer processes over IPC transport. If all of the filter sets are empty, every connection is accepted. Otherwise, credentials for a connecting process are checked against the filter sets and the connection is only accepted if a match is found. This commit is part of LIBZMQ-568 and only adds the filter sets and implements the filter in the IPC accept method. The interface for adding IDs to filter sets are included in a separate commit. IPC accept filtering is supported only on Linux and OS X.
-
- 25 Nov, 2013 1 commit
-
-
Chris Laws authored
-
- 17 Sep, 2013 2 commits
-
-
Pieter Hintjens authored
This reverts commit bfd472f9.
-
Laurent Alebarde authored
-
- 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).
-
- 09 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
* This is passed to the ZAP handler in the 'domain' field * If not set, or empty, then NULL security does not call the ZAP handler * This resolves the phantom ZAP request syndrome seen with sockets where security was never intended (e.g. in test cases) * This means if you install a ZAP handler, it will not get any requests for new connections until you take some explicit action, which can be setting a username/password for PLAIN, a key for CURVE, or the domain for NULL.
-
- 18 Aug, 2013 1 commit
-
-
Ian Barber authored
These were exposed to users, but have subsequently been removed as sockopts. They are currently only being used by ZAP, so I've moved it to a simpl function call (actually it's only used in one case even in that, so there may be a further simplification possible there).
-
- 17 Aug, 2013 1 commit
-
-
danielkr authored
-
- 29 Jun, 2013 1 commit
-
-
Martin Hurton authored
-