Age | Commit message (Collapse) | Author | |
---|---|---|---|
2010-10-08 | Clean-up of session termination process | Martin Sustrik | |
Specifically, shutdown of child objects is initiated *before* termination handshake with socket object. Signed-off-by: Martin Sustrik <sustrik@250bpm.com> | |||
2010-09-20 | problem with engine being attached to session while it's being terminated fixed | Martin Sustrik | |
2010-09-19 | obsolete 'active' flag removed from session_t | Martin Sustrik | |
2010-08-25 | elementary fixes to the named session | Martin Sustrik | |
2010-08-25 | engine termination on disconnect fixed | Martin Sustrik | |
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-03-20 | rollback of half-processed messages in case of disconnection | 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-02-13 | Multi-hop REQ/REP, part VIII., new blob_t type used for holding identity | Martin Sustrik | |
2010-02-13 | Multi-hop REQ/REP, part VII., identity-related algorithms rewritten | Martin Sustrik | |
2010-02-13 | Multi-hop REQ/REP, part VI., session 'name' renamed to 'peer_identity' | Martin Sustrik | |
2010-02-12 | Multi-hop REQ/REP, part V., peer identity is passed from init object to session | Martin Sustrik | |
2010-01-05 | Copyrights transferred from FastMQ to iMatix | Martin Sustrik | |
2009-12-23 | ZMQII-28: Bidirectional introduction on TCP connection establishment | Martin Sustrik | |
2009-12-15 | reconnection mechanism added to tcp transport | Martin Sustrik | |
2009-09-21 | initial version of req/rep sockets | Martin Sustrik | |
2009-09-16 | reconnect added to zmq_connecter | Martin Sustrik | |
2009-09-02 | python extension & perf tests | Martin Sustrik | |
2009-08-30 | engine virtualised; chatroom example removed | Martin Sustrik | |
2009-08-28 | pipe deallocation added | Martin Sustrik | |
2009-08-27 | multiple bugs fixed | Martin Sustrik | |
2009-08-27 | pipes added | Martin Sustrik | |
2009-08-21 | session management implemented | Martin Sustrik | |
2009-08-20 | couple of bugs in shutdown mechanism fixed | Martin Sustrik | |
2009-08-12 | listener/connecter/init/session added | Martin Sustrik | |
2009-08-06 | clean up - session/socket/engine stuff removed | Martin Sustrik | |
2009-08-03 | renamed from zs to zmq | Martin Sustrik | |
2009-07-29 | initial commit | Martin Sustrik | |