- 27 Aug, 2010 1 commit
-
-
Jon Dyte authored
-
- 26 Aug, 2010 1 commit
-
-
Ivo Danihelka authored
-
- 25 Aug, 2010 27 commits
-
-
Martin Sustrik authored
-
Martin Sustrik authored
-
Martin Sustrik authored
-
Martin Sustrik authored
-
Martin Sustrik authored
-
Martin Sustrik authored
-
Martin Sustrik authored
-
Martin Sustrik authored
-
Martin Sustrik authored
-
Martin Sustrik authored
-
Martin Sustrik authored
-
Martin Lucina authored
Trying to optimize out the case where items_[i]. events is 0 would result in a bogus pollfds[i]. Similarly in the select()-based impl, while not strictly necessary it's better to get ZMQ_FD even if events is 0 since that detects ETERM and friends.
-
Martin Lucina authored
Rewrite the select()-based zmq_poll() implementation to use ZMQ_FD and ZMQ_EVENTS. Also fix some corner cases: We should not pollute revents with unrequested events, and we don't need to poll on ZMQ_FD at all if a pollitem with no events set was passed in.
-
Martin Lucina authored
Dunno where those <TAB>s came from...
-
Martin Lucina authored
Rewrite zmq_poll() to use ZMQ_FD and ZMQ_EVENTS introduced on the wip-shutdown branch. Only do the poll()-based version of zmq_poll (), the select()-based version will not compile at the moment.
-
Martin Sustrik authored
-
Martin Sustrik authored
-
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.
-
Martin Sustrik authored
-
Martin Lucina authored
-
Martin Lucina authored
Add some basic documentation for XREQ/XREP socket types, including a brief description of the most common use case (REQ -> XREP) and (XREQ -> REP).
-
Pieter Hintjens authored
-
Pieter Hintjens authored
-
Pieter Hintjens authored
-
Martin Lucina authored
-
Martin Lucina authored
Function returning unsigned long int cannot return (-1)
-
- 21 Aug, 2010 2 commits
-
-
Pieter Hintjens authored
-
Pieter Hintjens authored
-
- 19 Aug, 2010 2 commits
-
-
Pieter Hintjens authored
-
Pieter Hintjens authored
-
- 18 Aug, 2010 1 commit
-
-
Martin Sustrik authored
-
- 11 Aug, 2010 3 commits
-
-
Pieter Hintjens authored
-
Pieter Hintjens authored
http://github.com/zeromq/zeromq2/issues#issue/46 Invalid messages are now discarded silently, instead of causing an assertion failure.
-
Pieter Hintjens authored
-
- 10 Aug, 2010 1 commit
-
-
Pieter Hintjens authored
-
- 08 Aug, 2010 1 commit
-
-
Pieter Hintjens authored
* Fixed zmq_term, zmq_socket, zmq_close, zmq_setsockopt, * zmq_getsockopt, zmq_bind, zmq_connect, zmq_send, * zmq_recv, zmq_poll, zmq_device, zmq_stopwatch_stop * Updated Reference Manual for these methods
-
- 07 Aug, 2010 1 commit
-
-
Pieter Hintjens authored
* zmq_term * zmq_socket * zmq_close * zmq_setsockopt * zmq_getsockopt * zmq_bind * zmq_connect * zmq_send * zmq_recv * zmq_poll * zmq_device * zmq_stopwatch_stop
-