- 13 Feb, 2016 1 commit
-
-
Luca Boccassi authored
Solution: use msleep (SETTLE_TIME) everywhere when waiting for the connections/sockets to be settled instead of a variety of patterns and functions to make tests more coherent.
-
- 12 Feb, 2016 1 commit
-
-
Pieter Hintjens authored
There were numerous small issues with test cases: - some lacked the right source file header - some were not portable at all - some were using internal libzmq APIs (headers) Solution: fixed and cleaned up.
-
- 06 Feb, 2016 2 commits
- 28 Jan, 2016 1 commit
-
-
Constantin Rack authored
Solution: update to 2016
-
- 28 Jul, 2015 1 commit
-
-
Brian Silverman authored
Under linux 3.16.0-4-amd64, I was getting occasional test failures before fixing this.
-
- 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 2 commits
-
-
Jonathan Reams authored
-
Jonathan Reams authored
This commit adds ZMTP connection heartbeats described in http://rfc.zeromq.org/spec:37/ZMTP.
-