Age | Commit message (Collapse) | Author | |
---|---|---|---|
2010-10-16 | ZMQ_LINGER socket option added. | Martin Sustrik | |
1. ZMQ_LINGER option can be set/get 2. options are part of own_t base class rather than being declared separately by individual objects 3. Linger option is propagated with "term" command so that the newest value of it is used rather than the stored old one. 4. Session sets the linger timer if needed and terminates as soon as it expires. 5. Corresponding documentation updated. Signed-off-by: Martin Sustrik <sustrik@250bpm.com> | |||
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-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-04-26 | P2P renamed to PAIR | Martin Sustrik | |