| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2010-09-30 | zmq_msg_move called on uninitialised message in xrep_t::xrecv -- fixed | Max Wolf | |
| 2010-09-30 | fix in XREP's fair queueing mechanism | Martin Sustrik | |
| 2010-09-28 | ZMQ_TYPE socket option added | Gonzalo Diethelm | |
| 2010-08-25 | I/O object hierarchy implemented | Martin Sustrik | |
| 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-08-11 | 46 - Devices vulnerable to invalid messages | Pieter Hintjens | |
| http://github.com/zeromq/zeromq2/issues#issue/46 Invalid messages are now discarded silently, instead of causing an assertion failure. | |||
| 2010-07-07 | issue 38 - Assertion failed: fetched (xrep.cpp:196) | Martin Hurton | |
| 2010-04-30 | prefix in XREP recv'd message misses MORE flag | Martin Sustrik | |
| 2010-04-27 | initial version of multi-hop REQ/REP | Martin Sustrik | |
| 2010-03-20 | XREP-style prefixing/trimming messages removed | Martin Sustrik | |
| 2010-03-13 | ZMQ_NOFLUSH and zmq_flush obsoleted | Martin Sustrik | |
| 2010-03-12 | Implement flow control fox ZMQ_XREP sockets | Martin Hurton | |
| 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-03-11 | Restructure language bindings | Martin Lucina | |
| C and C++ headers moved from bindings/ to include/, bindings/ removed --with-c and --with-cpp options to configure removed, C and C++ now built and installed by default | |||
| 2010-02-16 | Multi-hop REQ/REP, part XI., finalise the XREQ/XREP functionality | Martin Sustrik | |
| 2010-02-14 | Multi-hop REQ/REP, part X., optional delayed creation of pipes during connect | Martin Sustrik | |
| 2010-02-12 | Multi-hop REQ/REP, part III., change 'type' in options to simple ↵ | Martin Sustrik | |
| 'traceroute' flag | |||
| 2010-02-12 | Multi-hop REQ/REP, part I., socket type is known to all associated objects | 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 | zmq_streamer & zmq_queue are built under MSVC | unknown | |
| 2009-12-13 | XREP & XREQ socket types added; zmq_queue device added | Martin Sustrik | |
 |
index : libxs.git | |
| mato's libxs tree | Martin Lucina |
| summaryrefslogtreecommitdiff |