Age | Commit message (Collapse) | Author | |
---|---|---|---|
2011-01-26 | ZMQ_RECONNECT_IVL_MAX socket option added | Thijs Terlouw | |
It allows for exponential back-off strategy when reconnecting. Signed-off-by: Thijs Terlouw <thijsterlouw@gmail.com> | |||
2010-12-09 | Added Recovery Interval in Milliseconds | Bob Beaty | |
For very high-speed message systems, the memory used for recovery can get to be very large. The corrent limitation on that reduction is the ZMQ_RECOVERY_IVL of 1 sec. I added in an additional option ZMQ_RECOVERY_IVL_MSEC, which is the Recovery Interval in milliseconds. If used, this will override the previous one, and allow you to set a sub-second recovery interval. If not set, the default behavior is to use ZMQ_RECOVERY_IVL. Signed-off-by: Bob Beaty <rbeaty@peak6.com> | |||
2010-10-30 | Name of "GNU Lesser Public License" corrected. | Martin Sustrik | |
Signed-off-by: Martin Sustrik <sustrik@250bpm.com> | |||
2010-10-17 | ZMQ_BACKLOG socket option added. | Martin Sustrik | |
Signed-off-by: Martin Sustrik <sustrik@250bpm.com> | |||
2010-10-17 | ZMQ_RECONNECT_IVL socket options added. | Martin Sustrik | |
Signed-off-by: Martin Sustrik <sustrik@250bpm.com> | |||
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-09-28 | ZMQ_TYPE socket option added | Gonzalo Diethelm | |
2010-05-25 | LWM is computed rather than explicitly specified by user | Martin Sustrik | |
2010-04-09 | zmq_getsockopt function added | Martin Sustrik | |
2010-03-20 | XREP-style prefixing/trimming messages removed | 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-14 | Multi-hop REQ/REP, part X., optional delayed creation of pipes during connect | Martin Sustrik | |
2010-02-13 | Multi-hop REQ/REP, part IX., pass the peer identity as far as socket_base_t | 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-10 | ZMQII-27: Allow setting SNDBUF and RCVBUF size from 0MQ API (POSIX) | Martin Sustrik | |
2009-09-21 | different fixes to req/rep | Martin Sustrik | |
2009-09-21 | initial version of req/rep sockets | Martin Sustrik | |
2009-09-16 | added OpenPGM receiver - ZMQ_SUB | malosek | |
2009-09-14 | java binding sets socket options using setsockopt function | Martin Sustrik | |
2009-09-11 | added OpenPGM sender - ZMQ_PUB | malosek | |
2009-09-07 | initial changes for win port | unknown | |
2009-08-12 | listener/connecter/init/session added | Martin Sustrik | |