- 06 Mar, 2018 1 commit
-
-
Simon Giesecke authored
Solution: extracted common code into do_getsockopt/do_setsockopt functions
-
- 02 Feb, 2018 1 commit
-
-
sigiesec authored
Solution: applied clang-format
-
- 21 Oct, 2017 1 commit
-
-
Simon Giesecke authored
* Problem: excessive memory allocations around blob_t Solution: redefine blob_t as a custom type, and use reference/move semantics where possible
-
- 19 Sep, 2017 2 commits
- 07 Sep, 2017 2 commits
-
-
Doron Somech authored
-
sigiesec authored
Solution: renamed routing_id fields in pipe_t, renamed ZMQ_CONNECT_RID to ZMQ_CONNECT_ROUTING_ID
-
- 06 Sep, 2017 1 commit
-
-
sigiesec authored
Solution: replace by "routing id"
-
- 17 Sep, 2016 1 commit
-
-
Constantin Rack authored
Solution: replace tabes with spaces
-
- 18 Feb, 2016 1 commit
-
-
Osiris authored
Solution: Phase I - make precompiled.hpp be first file included in every source file
-
- 07 Feb, 2016 1 commit
-
-
Brian Silverman authored
Otherwise, it's undefined behavior. ubsan catches alignment issues in the libzmq test suite without this.
-
- 06 Feb, 2016 1 commit
-
-
Pieter Hintjens authored
There's no value in this as the same pattern is repeated in several places and it's fair to expect people to understand it. Solution: revert to the old, one-liner style.
-
- 05 Feb, 2016 1 commit
-
-
Brian Silverman authored
It's undefined behavior, and ubsan flags it.
-
- 28 Jan, 2016 1 commit
-
-
Constantin Rack authored
Solution: update to 2016
-
- 06 Sep, 2015 1 commit
-
-
Constantin Rack authored
-
- 21 Aug, 2015 2 commits
-
-
Joe Eli McIlvain authored
Solution: Move the macros to a private header.
-
reza.ebrahimi authored
-
- 14 Aug, 2015 1 commit
-
-
reza.ebrahimi authored
-
- 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.
-
- 22 Apr, 2015 1 commit
-
-
evoskuil authored
-
- 19 Feb, 2015 1 commit
-
-
Thomas Rodgers authored
-
- 18 Feb, 2015 1 commit
-
-
Thomas Rodgers authored
-
- 11 Feb, 2015 1 commit
-
-
evoskuil 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
-
- 21 Jan, 2014 1 commit
-
-
Tim M authored
Added assert on duplicate id in ROUTER and STREAM sockets. Updated man to reflect this change. Modified test case to match.
-
- 20 Jan, 2014 1 commit
-
-
Tim M authored
Updated man entries, and added behavior in case the user duplicates peer ids. In this case the socket reverts to default behavior.
-
- 19 Jan, 2014 3 commits
-
-
Tim M authored
-
Pieter Hintjens authored
- renamed to ZMQ_CONNECT_RID - fixed whitespace malformating around previous patch - renamamed next_peer_id to next_rid in preparation for larger rename of IDENTITY to ROUTING_ID Note: ZMQ_CONNECT_RID has no test case and no entry in the man page, as yet.
-
Tim M authored
Fixed compile issue with missing member of socket_base. Changed ZMQ_NEXT_IDENTITY to ZMQ_NEXT_CONNECT_PEER_ID. Fixed case where ZMQ_NEXT_CONNECT_PEER_ID is used in ROUTER, and ROUTER does not read the identity message from the connected pipe.
-
- 18 Jan, 2014 1 commit
-
-
Matt Arsenault authored
-
- 17 Jan, 2014 1 commit
-
-
Tim M authored
Both STREAM and ROUTER sockets suffer from a naming problem on outbound connections. While these connections can be created, they can't be immediately used. Traffic must be received before it can be sent. This prevents practical, minimal usage of STREAM or ROUTER as a true N fan in/out socket. This change simply provides the user with a socket option that sets a user defined name of the next outbound connection: zmq_setsockopt(routerSock,ZMQ_NEXT_IDENTITY,"myname",6); if(0 > zmq_connect(routerSock,"tcp://127.0.0.1:1234")) return 1; ret = zmq_send(routerSock,"myname",6,ZMQ_SNDMORE); zmq_send(routerSock,b.mem,b.used,0); In this example, the socket is immediately given the name "myname", and is capable of immediately sending traffic. This approach is more effective in three ways: 1) It prevents all sorts of malicious peer naming attacks that can cause undefined behavior in existing ROUTER connections. (Two connections are made that both transmit the same name to the ROUTER, the ROUTER behavior is undefined) 2) It allows immediate control of connections made to external parties for STREAM sockets. Something that is not possible right now. Before an outbound connection had no name for STREAM or ROUTER sockets because outbound connections cannot be sent to without first receiving traffic. 3) It is simpler and more general than expecting two ROUTER sockets to handshake on assigned connection names. Plus it allows inline sending to new connections on ROUTER.
-
- 02 Jan, 2014 1 commit
-
-
Pieter Hintjens authored
-
- 28 Oct, 2013 1 commit
-
-
Pieter Hintjens authored
* The ZMQ_ROUTER_RAW API was deprecated in favor of ZMQ_STREAM * Same issue hit router.cpp, which I've fixed
-
- 31 Aug, 2013 1 commit
-
-
Shawn J. Goff authored
icanhasall is cute (for now), but the effect of the variable is clear only after tracking down its origin reading the commit. This change is intended to make it easier for people to have some intuition about its effect from its name.
-
- 29 Jun, 2013 2 commits
-
-
Martin Hurton authored
-
Martin Hurton authored
-
- 28 Jun, 2013 2 commits
-
-
Martin Hurton authored
-
Martin Hurton authored
-