- 19 Sep, 2017 2 commits
-
-
sigiesec authored
Solution: replace by "routing id"
-
Luca Boccassi authored
Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
-
- 18 Sep, 2017 1 commit
-
-
sigiesec authored
mechanisms Solution: uniformly require a ZAP domain to be set to activate ZAP handling, clarify comment on Stonehouse pattern
-
- 07 Sep, 2017 1 commit
-
-
Doron Somech authored
-
- 06 Sep, 2017 1 commit
-
-
sigiesec authored
Solution: replace by "routing id"
-
- 04 Sep, 2017 1 commit
-
-
pavel.pimenov authored
The '||' operator is surrounded by opposite expressions. session_base.cpp 377
-
- 01 Sep, 2017 2 commits
-
-
Luca Boccassi authored
Solution: add /* FALLTHROUGH */ comments so that nagging compilers don't nag
-
sigiesec authored
pending termination while processing an error Solution: terminate pipe instead Fixes #2723
-
- 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 Jul, 2017 1 commit
-
-
Luca Boccassi authored
Solution: if a CURVE server is using zmq_connect, the same session will be used for any client "reconnect" (actual binds). This is acceptable, so do not assert if zap_pipe already exists during the handshake, but simply reuse it. Fixes #2608
-
- 13 Jun, 2017 1 commit
-
-
Luca Boccassi authored
Solution: if inproc://zeromq.zap.01 exists, which means ZAP is enabled, abort immediately if it cannot be used (eg: out of memory) or it is configured incorrectly (eg: wrong socket type). Otherwise authentication failures will simply be ignored and unauthorised peers will be allowed to slip in.
-
- 12 Jun, 2017 1 commit
-
-
sunddy authored
problem: for zmq radio/dish pattern, if the radio process restarts, the dish will not resend subscriptions to radio. And the result is that the dish will never receive any more messages. solution: in session_base_t::reconnect (), take ZMQ_DISH into consideration when invoking hiccup method.
-
- 02 Jun, 2017 1 commit
-
-
laplaceyang authored
In function session_base_t::reconnect, if we set immediate to 1 and set linger, we will get into first block of reconnect function, and set pipe to NULL, but we forget to cancel timer of linger. Once timer tiggered, we will get coredump. Solution: cancel timer in the end of set pipe to NULL
-
- 29 Mar, 2017 2 commits
- 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 May, 2016 1 commit
-
-
Bitiquinho authored
-
- 08 May, 2016 1 commit
-
-
hitstergtd authored
Solution: Indent it.
-
- 21 Apr, 2016 1 commit
-
-
somdoron authored
-
- 18 Feb, 2016 1 commit
-
-
Osiris authored
Solution: Phase I - make precompiled.hpp be first file included in every source file
-
- 29 Jan, 2016 2 commits
- 28 Jan, 2016 1 commit
-
-
Constantin Rack authored
Solution: update to 2016
-
- 27 Jan, 2016 1 commit
-
-
somdoron authored
-
- 17 Dec, 2015 1 commit
-
-
Pieter Hintjens authored
This reverts commit 54799c8c. This change broke the tests/test_shutdown_stress testcase.
-
- 08 Dec, 2015 1 commit
-
-
Ilya Kulakov authored
VMCI transport allows fast communication between the Host and a virtual machine, between virtual machines on the same host, and within a virtual machine (like IPC). It requires VMware to be installed on the host and Guest Additions to be installed on a guest.
-
- 30 Nov, 2015 1 commit
-
-
Charles Stanley 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
-
- 06 Aug, 2015 1 commit
-
-
Soren Hansen authored
While sending very large messages (far beyond what fits in a the tcp buffer, so it takes multiple sendto system calls for it to finish), zmq_close will close the connection regardless of ZMQ_LINGER. In case no engine is attached, a pipe->check_read() is needed to look for the delimiter in the pipe and ultimately trigger the pipe termination. However, if there *is* an engine attached, the check_read() looks ahead and finds the delimiter and terminates the connection even though the engine might actually still be in the middle of sending a message. This happens because while the io_thread is still busy sending the data, the pipe can get terminated and the io thread ends up being terminated.
-
- 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.
-
- 02 Feb, 2015 1 commit
-
-
somdoron authored
-
- 01 Feb, 2015 1 commit
-
-
somdoron 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
-
- 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
-
- 03 Dec, 2014 1 commit
-
-
Min RK authored
checks mechanism != NULL, or NULL + non-empty zap_domain
-
- 09 Oct, 2014 1 commit
-
-
Pavel Pimenov authored
Fix V815 Decreased performance. Consider replacing the expression 'options.socks_proxy_address != ""' with '!options.socks_proxy_address.empty()'. session_base.cpp 497
-