- 22 Jun, 2011 1 commit
-
-
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>
-
- 21 Apr, 2011 1 commit
-
-
Martin Sustrik authored
This patch addresses serveral issues: 1. It gathers message related functionality scattered over whole codebase into a single class. 2. It makes zmq_msg_t an opaque datatype. Internals of the class don't pollute zmq.h header file. 3. zmq_msg_t size decreases from 48 to 32 bytes. That saves ~33% of memory in scenarios with large amount of small messages. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 02 Mar, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 13 Jan, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 05 Nov, 2010 1 commit
-
-
Martin Sustrik authored
Threads were so far identified by integers called 'slots'. This patch renames them to more comprehensible 'tid's (thread IDs). Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 30 Oct, 2010 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 25 Aug, 2010 2 commits
-
-
Martin Sustrik authored
-
Martin Sustrik authored
Sockets may now be migrated between OS threads; sockets may not be used by more than one thread at any time. To migrate a socket to another thread the caller must ensure that a full memory barrier is called before using the socket from the target thread. The new zmq_close() semantics implement the behaviour discussed at: http://lists.zeromq.org/pipermail/zeromq-dev/2010-July/004244.html Specifically, zmq_close() is now deterministic and while it still returns immediately, it does not discard any data that may still be queued for sending. Further, zmq_term() will now block until all outstanding data has been sent. TODO: Many bugs have been introduced, needs testing. Further, SO_LINGER or an equivalent mechanism (possibly a configurable timeout to zmq_term()) needs to be implemented.
-
- 27 Mar, 2010 2 commits
-
-
Martin Sustrik authored
-
Martin Sustrik authored
-
- 13 Mar, 2010 1 commit
-
-
Martin Sustrik authored
-
- 12 Mar, 2010 2 commits
-
-
Martin Hurton authored
-
Martin Hurton authored
This commit introduces the necessary changes necessary for implementing flow control. None of the socket types implements the flow control yet. The code will crash when the flow control is enabled and the thw lwm is reached. The following commits will add flow-control support for individual socket types.
-
- 16 Feb, 2010 1 commit
-
-
Martin Sustrik authored
-
- 05 Jan, 2010 1 commit
-
-
Martin Sustrik authored
-
- 24 Nov, 2009 1 commit
-
-
Martin Sustrik authored
-
- 01 Oct, 2009 1 commit
-
-
Martin Sustrik authored
-
- 23 Sep, 2009 1 commit
-
-
Martin Sustrik authored
-
- 21 Sep, 2009 2 commits
-
-
Martin Sustrik authored
-
Martin Sustrik authored
-
- 06 Aug, 2009 1 commit
-
-
Martin Sustrik authored
-
- 03 Aug, 2009 1 commit
-
-
Martin Sustrik authored
-
- 29 Jul, 2009 1 commit
-
-
Martin Sustrik authored
-