- 08 Aug, 2017 1 commit
-
-
Simon Giesecke authored
* Problem: missing test for status code 300, inadequate assertion for status code 500 Solution: add test, change assertion (currently test fails) * Problem: gcc compiler error deprecated conversion from string constant Solution: declare variable as const * Problem: in case of ZAP handler returning a status code other than 200, no appropriate event is emitted Solution: immediately emit event after receiving reply from ZAP handler * Problem: endpoint address is not included in zap-reply monitor event Solution: added functions to retrieve endpoint address in zmq::i_engine and zmq::session_base_t removed unused code block in zmq::stream_engine_t::next_handshake_command * Problem: wrong formatting Solution: fix formatting * Problem: test fails because of EPIPE Solution: add EPIPE/ECONNRESET/ECONNAGAIN handling for more test cases
-
- 01 Jan, 2017 1 commit
-
-
Vincent Tellier authored
- removed the previously added encryption_error, less changes less bug - handshake fail is now signaled when an error happen while the mechanism is still hanshaking
-
- 30 Dec, 2016 1 commit
-
-
Vincent Tellier authored
Added two new monitoring events: - ZMQ_EVENT_HANDSHAKE_SUCCEED is raised once the encryption handshake succeed - ZMQ_EVENT_HANDSHAKE_FAILED is raised when it failed Both events are raised on server and client side.
-
- 15 Dec, 2016 1 commit
-
-
laplaceyang authored
-
- 14 May, 2016 1 commit
-
-
evoskuil authored
-
- 28 Jan, 2016 1 commit
-
-
Constantin Rack authored
Solution: update to 2016
-
- 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.
-
- 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 Feb, 2015 1 commit
-
-
Thomas Rodgers authored
-
- 18 Feb, 2015 1 commit
-
-
Thomas Rodgers authored
-
- 22 Jan, 2015 1 commit
-
-
Pieter Hintjens authored
Solution: update for 2015 Fixes #1320
-
- 09 Jan, 2015 1 commit
-
-
Thomas Rodgers authored
Revert "linking fd to pipe identity via socket option" This reverts commit fe3e8c5c. Conflicts: include/zmq.h src/pipe.hpp src/session_base.cpp
-
- 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
-
- 17 May, 2014 1 commit
-
-
Martin Hurton authored
-
- 09 May, 2014 1 commit
-
-
Will Strang authored
-
- 05 May, 2014 1 commit
-
-
Martin Hurton authored
-
- 02 May, 2014 1 commit
-
-
Martin Hurton authored
Metadata are built in stream_engine now. This makes it easy to extend metadata with user-defined properties.
-
- 30 Apr, 2014 1 commit
-
-
Stoian Ivanov authored
-
- 12 Jan, 2014 1 commit
-
-
Martin Hurton authored
The get_credential () member function returns credential for the last peer we received message for. The idea is that this function is used to implement user-level API.
-
- 02 Jan, 2014 2 commits
-
-
AJ Lewis authored
This reverts commit f27eb67e, reversing changes made to a3ae0d4c. https://zeromq.jira.com/browse/LIBZMQ-576 Conflicts: src/stream_engine.cpp Conflicts were around additional defaults to the constructor after the 'terminating' default. The additional defaults were left alone, and the 'terminating' default was removed.
-
Pieter Hintjens authored
-
- 07 Nov, 2013 1 commit
-
-
Martin Hurton authored
-
- 09 Oct, 2013 1 commit
-
-
Martin Hurton authored
-
- 04 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
* Command names changed from null terminated to length-specified * Command frames use the correct flag (bit 2) * test_stream acts as test case for command frames * Some code cleanups
-
- 18 Jul, 2013 1 commit
-
-
Martin Hurton authored
-
- 22 Jun, 2013 1 commit
-
-
Martin Hurton authored
-
- 21 Jun, 2013 1 commit
-
-
Ian Barber authored
-
- 06 Jun, 2013 1 commit
-
-
Martin Hurton authored
-
- 17 May, 2013 1 commit
-
-
Pieter Hintjens authored
- we need to switch to PLAIN according to options.mechanism - we need to catch case when both peers are as-server (or neither is) - and to use username/password from options, for client
-
- 14 May, 2013 2 commits
-
-
Martin Hurton authored
This implements protocol handshake. We still need to design and implement 1) API changes so a user can set username and password, and 2) a mechanism for engine to authenticate users.
-
Martin Hurton authored
-
- 28 Apr, 2013 1 commit
-
-
Martin Hurton authored
-
- 12 Apr, 2013 1 commit
-
-
Martin Hurton authored
The patch makes the code somewhat simpler and prepares it for more complex initialization handshakes.
-
- 11 Apr, 2013 1 commit
-
-
Martin Hurton authored
-
- 12 Mar, 2013 3 commits
-
-
Pieter Hintjens authored
-
Pieter Hintjens authored
* Starting draft ZMTP/2.1 protocol (revision 2) * Basis for adding security to the wire protocol * Maintains backward compatibility
-
Pieter Hintjens authored
Copyrights had become ads for Sustrik's corporate sponsors, going against the original agreement to share copyrights with the community (that agreement was: one line stating iMatix copyright + one reference to AUTHORS file). The proliferation of corporate ads is also unfair to the many individual authors. I've removed ALL corporate title from the source files so the copyright statements can now be centralized in AUTHORS and source files can be properly updated on an annual basis.
-
- 01 Feb, 2013 1 commit
-
-
Min(Dongmin Yu) authored
When we send a large message, the message can be splitted into two chunks. One is in the encoder buffer and the other is the zero-copy pointer. The session could get the term before the last chunk is sent.
-
- 02 Jan, 2013 1 commit
-
-
Matt Arsenault authored
Fix warnings with ICC.
-