Age | Commit message (Collapse) | Author | |
---|---|---|---|
2010-07-30 | XREQ: Correct behaviour on hitting ZMQ_HWM | Martin Lucina | |
This reverts part of commit 84e0c7991a9b316ed571533abc628cc1175750a3 to get correct ZMQ_HWM semantics with XREQ sockets: When sending a message to an XREQ socket, the underlying pipe is selected in a round-robin fashion. If an underlying pipe is full it is skipped. If there are no underlying pipes, or all underlying pipes are full then zmq_send() shall block or return EAGAIN, depending on whether or not the call is blocking. Messages are never dropped. | |||
2010-05-02 | queue device fixed | Martin Sustrik | |
2010-03-13 | ZMQ_NOFLUSH and zmq_flush obsoleted | 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-02-16 | Multi-hop REQ/REP, part XI., finalise the XREQ/XREP functionality | Martin Sustrik | |
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 | |||
2009-12-13 | XREP & XREQ socket types added; zmq_queue device added | Martin Sustrik | |