- 02 Apr, 2016 1 commit
-
-
Frederic Tregon authored
Problem: Since pull request #1730 was merged, protocol for REQ socket is checked at the session level and this check does not take into account the possibility of a request_id being part of the message. Thus the option ZMQ_REQ_CORRELATE would no longer work. This is now fixed: the possiblity of a 4 bytes integer being present before the delimiter frame is taken into account (whether or not this breaks the REQ/REP RFC is another issue).
-
- 20 Mar, 2016 1 commit
-
-
Frederic Tregon authored
Problem: when using ZMQ_REQ_RELAXED + ZMQ_REQ_CORRELATE and two 'send' are executed in a row and no server is available at the time of the sends, then the internal request_id used to identify messages gets corrupted and the two messages end up with the same request_id. The correlation no longer works in that case and you may end up with the wrong message. Solution: make a copy of the request_id instance member before sending it down the pipe.
-
- 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.
-
- 28 Jan, 2016 2 commits
-
-
somdoron authored
-
Constantin Rack authored
Solution: update to 2016
-
- 03 Jan, 2016 1 commit
-
-
Frederic Tregon authored
Current ZMQ_REQ_RELAXED test improvement to check that pipes are not closed after executing two send() in a row with no recv() in between.
-
- 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.
-
- 30 Jan, 2015 1 commit
-
-
Pieter Hintjens authored
Solution: raise timeouts from 100-150 msec to 250 msec
-
- 22 Jan, 2015 1 commit
-
-
Pieter Hintjens authored
Solution: update for 2015 Fixes #1320
-
- 02 Jan, 2014 1 commit
-
-
Pieter Hintjens authored
-
- 06 Nov, 2013 1 commit
-
-
Pieter Hintjens authored
- used msleep (10) in most places instead of zmq_sleep (1) - may cause failures on slower machines - to change, modify SETTLE_TIME in testutil.h - tested down to 1 msec on fast boxes
-
- 20 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
* ZMQ_REQ_STRICT was negative option (default 1) which goes against the standard, where defaults are zero. I renamed this to ZMQ_REQ_RELAXED. * ZMQ_REQ_REQUEST_IDS felt clumsy and describes the technical solution rather than the problem/requirement. I changed to ZMQ_REQ_CORRELATE which seems more explicit.
-
- 18 Sep, 2013 1 commit
-
-
Markus Rothe authored
-
- 15 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
* Removed redundant Z85 code and include files from project * Simplified use of headers in test cases (now they all just use testutil.hpp) * Export zmq_z85_encode() and zmq_z85_decode() in API * Added man pages for these two functions
-
- 17 Aug, 2013 1 commit
-
-
Richard Newton authored
-
- 03 Aug, 2013 1 commit
-
-
Christian Kamm authored
It defaults to enabled. Switch it off to be able to send a new message before the previous reply has been received.
-
- 28 Jul, 2013 1 commit
-
-
Christian Kamm authored
This allows making a new request on a REQ socket by sending a new message. Without the option set, calling send() after the first message is done will continue to return an EFSM error. It's useful for when a REQ is not getting a response. Previously that meant creating a new socket or switching to DEALER.
-