- 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>
-
- 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>
-
- 02 Mar, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 09 Feb, 2011 2 commits
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
Martin Sustrik authored
Reaper thread destroys the socket asynchronously. zmq_term() can be interrupted by a signal (EINTR). zmq_socket() will return ETERM after zmq_term() was called. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 05 Nov, 2010 2 commits
-
-
Martin Sustrik authored
For historical reasons queue to transfer commands between threads was called 'signaler'. Given that it was used to pass commands rather than signals it was renamed to 'mailbox', see Erlang mailboxes. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
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>
-
- 26 Sep, 2010 1 commit
-
-
Martin Sustrik authored
-
- 25 Aug, 2010 1 commit
-
-
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.
-
- 05 May, 2010 1 commit
-
-
Martin Sustrik authored
-
- 29 Apr, 2010 3 commits
-
-
Martin Sustrik authored
-
Martin Sustrik authored
-
Martin Sustrik authored
-
- 05 Jan, 2010 1 commit
-
-
Martin Sustrik authored
-
- 15 Dec, 2009 1 commit
-
-
Martin Sustrik authored
-
- 02 Oct, 2009 1 commit
-
-
Martin Sustrik authored
-
- 20 Sep, 2009 1 commit
-
-
Martin Sustrik authored
-
- 09 Aug, 2009 1 commit
-
-
Martin Sustrik authored
-
- 08 Aug, 2009 1 commit
-
-
Martin Sustrik authored
-
- 06 Aug, 2009 2 commits
-
-
Martin Sustrik authored
-
Martin Sustrik authored
-
- 03 Aug, 2009 1 commit
-
-
Martin Sustrik authored
-
- 29 Jul, 2009 1 commit
-
-
Martin Sustrik authored
-