- 14 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: Use size_t instead of int
-
- 02 Feb, 2018 1 commit
-
-
sigiesec authored
Solution: applied clang-format
-
- 19 Sep, 2017 2 commits
- 07 Sep, 2017 1 commit
-
-
Doron Somech authored
-
- 06 Sep, 2017 1 commit
-
-
sigiesec authored
Solution: replace by "routing id"
-
- 01 May, 2017 1 commit
-
-
Luca Boccassi authored
Solution: use ZMQ_LAST_ENDPOINT in most places. This alllows running tests in paralle, and on over-booked shared machines where many of the ports would be already in use. Keep 3 tests with an hardcoded port, as there are some code paths that require it (eg: connect before bind), but list those ports in tests/testutil.hpp as macros so that they do not overlap and still allow parallel runs. These changes were inspired by a patch uploaded to Ubuntu by the package maintainer, Steve Langasek <steve.langasek@ubuntu.com>. Thank you Steve!
-
- 28 Jan, 2016 1 commit
-
-
Constantin Rack authored
Solution: update to 2016
-
- 20 Aug, 2015 1 commit
-
-
Joe Eli McIlvain authored
Solution: Convert to spaces and remove trailing whitespace in these files.
-
- 22 Jul, 2015 1 commit
-
-
Brian Silverman authored
I traced memory leaks found using AddressSanitizer down to these.
-
- 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.
-
- 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
-
- 23 Jan, 2014 1 commit
-
-
Pieter Hintjens authored
- renamed test_stream_disconnect_notifications (too long!) - removed print statements in that test case - fixed Makefile.am for test_zap_ipc_creds (was not building)
-
- 18 Jan, 2014 1 commit
-
-
Matt Arsenault authored
-
- 17 Jan, 2014 1 commit
-
-
Goswin von Brederlow authored
Adjust test cases to connection notification. Increase error checking in test cases.
-
- 15 Jan, 2014 1 commit
-
-
Andre Caron authored
When a ZMQ_STREAM socket connection is broken (intentionally, via `shutdown()` or accidentally via client crash or network failure), there is no way for the application to dertermine that it should drop per-connection data (such as buffers). This contribution makes sure the application receives a 0-length message to notify it that the connection has been broken. This is symmetric with the process of closing the connection from within the application (where the application sends a 0-length message to tell ZeroMQ to close the connection). Conflicts: CMakeLists.txt
-