- 19 Jan, 2014 1 commit
-
-
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.
-
- 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.
-
- 08 Jan, 2014 1 commit
-
-
Martin Hurton authored
-
- 02 Jan, 2014 1 commit
-
-
Pieter Hintjens authored
-
- 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 3 commits
-
-
Martin Hurton authored
-
Martin Hurton authored
-
Martin Hurton authored
-
- 27 Jun, 2013 1 commit
-
-
Pieter Hintjens authored
- designed for TCP clients and servers - added HTTP client / server example in tests/test_stream.cpp - same as ZMQ_ROUTER + ZMQ_ROUTER_RAW + ZMQ_ROUTER_MANDATORY - includes b893ce set ZMQ_IDENTITY on outgoing connect - deprecates ZMQ_ROUTER_RAW
-
- 06 Jun, 2013 1 commit
-
-
Martin Hurton authored
-
- 05 Jun, 2013 1 commit
-
-
Pieter Hintjens authored
- renamed to ZMQ_PROBE_ROUTER
-
- 23 May, 2013 1 commit
-
-
shripchenko authored
implement it for DEALER tocket. +documentation
-
- 21 May, 2013 2 commits
-
-
shripchenko authored
Add ROUTER socket option to introduce self(send an empty message) to new peers, to allow ROUTER<->ROUTER auto-discovery problem.
-
root authored
Add ROUTER socket option to introduce self(send an empty message) to new peers, to allow ROUTER<->ROUTER auto-discovery problem.
-
- 12 Mar, 2013 1 commit
-
-
Pieter Hintjens authored
Copyrights had become ads for Sustrik's corporate sponsors, going against the original agreement to share copyrights with the community (that agreement was: one line stating iMatix copyright + one reference to AUTHORS file). The proliferation of corporate ads is also unfair to the many individual authors. I've removed ALL corporate title from the source files so the copyright statements can now be centralized in AUTHORS and source files can be properly updated on an annual basis.
-
- 09 Nov, 2012 2 commits
-
-
Martin Hurton authored
-
Martin Hurton authored
-
- 29 Oct, 2012 1 commit
-
-
Hardeep authored
- Created a new option ZMQ_ROUTER_RAW_SOCK - Added new raw_encoder and raw_decoder to receive and send messages in raw form to remote client - Added test case file tests/test_raw_sock.cpp o To create a raw router sock set the ZMQ_ROUTER_RAW_SOCK option o ZMQ_MSGMORE flag is ignored for non-id messages o To terminate a remote connection send id message followed by zero length data message
-
- 08 Oct, 2012 1 commit
-
-
Pieter Hintjens authored
-
- 16 Jun, 2012 1 commit
-
-
Kobolog authored
-
- 02 Apr, 2012 1 commit
-
-
Martin Hurton authored
The new implementation allows one to send messages through a router socket to a peer even before receiving messages from this peer. Fixes issue #304
-
- 22 Mar, 2012 1 commit
-
-
Pieter Hintjens authored
-
- 20 Mar, 2012 1 commit
-
-
Pieter Hintjens authored
* Implemented new ctx API (_new, _destroy, _get, _set) * Removed 'typesafe' macros from zmq.h * Added support for MAX_SOCKETS (was tied into change for #337) * Created new man pages
-
- 15 Mar, 2012 2 commits
- 16 Feb, 2012 1 commit
-
-
Staffan Gimåker authored
This allows us to actually report an error to the caller on resolve failure, rather than asserting later on in the io thread. Signed-off-by:
Staffan Gimåker <staffan@spotify.com>
-
- 02 Feb, 2012 1 commit
-
-
Martin Lucina authored
With the introduction of subscription forwarding, the first message sent on a PUB socket using a unidirectional transport (e.g. PGM) is always lost due to the "subscribe to all" being done asynchronously. This patch fixes the problem and also refactors the code to have a single point where the "subscribe to all" is performed. Signed-off-by:
Martin Lucina <martin@lucina.net>
-
- 17 Dec, 2011 1 commit
-
-
Martin Sustrik authored
When polling on XREP socket in incoming message part was prefetched, but not the identity of sender. The problem is fixed by this patch. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 09 Nov, 2011 1 commit
-
-
AJ Lewis authored
Older versions of gcc have problems with in-line forward declarations when there's a naming conflict with a global symbol. Signed-off-by:
AJ Lewis <aj.lewis@quantum.com> Expand the original patch to all such forward declarations. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 04 Nov, 2011 1 commit
-
-
Martin Sustrik authored
However, the "durable socket" behaviour wasn't re-added. Identities are used solely for routing in REQ/REP pattern. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 01 Nov, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 31 Oct, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 15 Sep, 2011 1 commit
-
-
Martin Sustrik authored
This is a preliminary patch allowing for socket-type-specific functionality in the I/O thread. For example, message format can be checked asynchronously and misbehaved connections dropped straight away. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 15 Jul, 2011 1 commit
-
-
Martin Sustrik authored
This patch simplifies the whole codebase significantly, including dropping depedency on libuuid. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 22 Jun, 2011 2 commits
-
-
Martin Sustrik authored
Up to now the complexity of fair-queueing in XREP was O(n). Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
Martin Sustrik authored
This patch introduces two changes: 1. 32-bit ID is used to identify the peer instead of UUID 2. REQ socket seeds the label stack with unique 32-bit request ID It also drops any replies with non-matching request ID Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 23 May, 2011 1 commit
-
-
Martin Sustrik authored
So far, the pipe termination code was spread among socket type classes, fair queuer, load balancer, etc. This patch moves all the associated logic to a single place. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 22 May, 2011 1 commit
-
-
Martin Sustrik authored
So far, there was a pair of unidirectional pipes between a socket and a session (or an inproc peer). This resulted in complex problems with half-closed states and tracking which inpipe corresponds to which outpipe. This patch doesn't add any functionality in itself, but is essential for further work on features like subscription forwarding. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-