- 30 Nov, 2015 1 commit
-
-
Chris authored
Only start the heartbeat timer when the underlying mechanism is ready to stop cipher streams from trying to encrypt a heartbeat before the handshake has completed. Addresses issue #1601.
-
- 18 Nov, 2015 1 commit
-
-
somdoron authored
-
- 08 Nov, 2015 1 commit
-
-
Jens Auer authored
-
- 08 Oct, 2015 1 commit
-
-
Jens Auer authored
-
- 21 Aug, 2015 1 commit
-
-
Joe Eli McIlvain authored
Solution: Move the macros to a private header.
-
- 16 Aug, 2015 1 commit
-
-
reza.ebrahimi authored
-
- 23 Jul, 2015 1 commit
-
-
KIU Shueng Chuan authored
-
- 26 Jun, 2015 1 commit
-
-
Jonathan Reams authored
Set the ZMQ_HEARTBEAT_TIMEOUT to default to the value of ZMQ_HEARTBEAT_IVL if it's not explicitly set. Change the units of ZMQ_HEARTBEAT_TTL to milliseconds in the API and round down to the nearest decisecond so that all the options are using the same units. Make the maximum heartbeat TTL match the spec (6553 seconds)
-
- 24 Jun, 2015 1 commit
-
-
Jonathan Reams authored
This commit adds ZMTP connection heartbeats described in http://rfc.zeromq.org/spec:37/ZMTP.
-
- 14 Jun, 2015 1 commit
-
-
Jens Auer authored
zero-copy msg_t::init cannot be used when the message exceeds either the buffer end or the last received byte. To detect this, the buffer is now resized to the numnber of received bytes.
-
- 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.
-
- 19 May, 2015 1 commit
-
-
Brian Knox authored
-
- 22 Apr, 2015 1 commit
-
-
evoskuil authored
-
- 19 Feb, 2015 2 commits
-
-
Thomas Rodgers authored
-
Thomas Rodgers authored
-
- 18 Feb, 2015 1 commit
-
-
Thomas Rodgers authored
-
- 27 Jan, 2015 1 commit
-
-
Thomas Rodgers authored
-
- 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
-
- 16 Jan, 2015 3 commits
-
-
Thomas Rodgers authored
-
Thomas Rodgers authored
std::map::insert() has always had range based insertion, removed explicit loops.
-
Thomas Rodgers authored
Allows non-C/C++ based clients easy access to the peer's IP address via zmq_msg_gets(&msg, "Peer-Address") instead of zmq_msg_get(&msg, ZMQ_SRCFD) followed by calls to getpeername and getnameinfo
-
- 19 Dec, 2014 1 commit
-
-
Pieter Hintjens authored
E.g. when server is not configured, and client tries PLAIN security, there is no hint of why this does not work. Solution: add debugging output for this case. Note that the various debugging outputs for security failures should probably be sent to an inproc monitor of some kind.
-
- 03 Dec, 2014 2 commits
- 09 Oct, 2014 2 commits
-
-
Pavel Pimenov authored
Fix V815 Decreased performance. Consider replacing the expression 'peer_address = ""' with 'peer_address.clear()'. stream_engine.cpp 99
-
Pavel Pimenov authored
Fix V803 Decreased performance. In case 'it' is iterator it's more effective to use prefix form of increment. Replace iterator++ with ++iterator. stream_engine.cpp http://www.viva64.com/en/d/0165/print/
-
- 19 Sep, 2014 1 commit
-
-
Pieter Hintjens authored
Solution: accept only the mechanism defined by the socket options. I've not tested this yet, so it's a speculative fix.
-
- 03 Jul, 2014 1 commit
-
-
Rodrigo Mosconi 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
-
- 18 May, 2014 1 commit
-
-
Martin Hurton authored
-
- 17 May, 2014 1 commit
-
-
Martin Hurton authored
-
- 12 May, 2014 1 commit
-
-
Martin Hurton authored
-
- 09 May, 2014 1 commit
-
-
Will Strang authored
-
- 07 May, 2014 1 commit
-
-
Martin Hurton authored
NULL mechanism sends ERROR command rather than READY command when ZAP handler rejects the ZAP request (status code != "200"). The body of ERROR command contains the status code as returned by ZAP handler.
-
- 06 May, 2014 1 commit
-
-
Martin Hurton authored
-
- 05 May, 2014 1 commit
-
-
Martin Hurton authored
-
- 03 May, 2014 1 commit
-
-
Martin Hurton authored
We use metadata_t directly. No need for generic interface now.
-
- 02 May, 2014 2 commits
-
-
Pieter Hintjens authored
-
Pieter Hintjens authored
- also prioritize ZAP metadata over ZMTP metadata in case application uses same names.
-