Age | Commit message (Collapse) | Author | |
---|---|---|---|
2010-08-25 | WIP: Socket migration between threads, new zmq_close() semantics | Martin Sustrik | |
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. | |||
2010-03-27 | ZMQ_TBC renamed to ZMQ_MORE | Martin Sustrik | |
2010-03-27 | multi-part message work with UPSTREAM/DOWNSTREAM | Martin Sustrik | |
2010-03-12 | Implement flow control | Martin Hurton | |
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. | |||
2010-01-05 | Copyrights transferred from FastMQ to iMatix | Martin Sustrik | |
2009-12-15 | zmq_encoder/decoder are able to add/trim prefixes from messages; fair ↵ | Martin Sustrik | |
queueing and load balancing algorithms factorised into separate classes |