summaryrefslogtreecommitdiff
path: root/doc
AgeCommit message (Collapse)Author
2011-11-01LABELs removed from the documentationMartin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-10-06Default HWMs are set to 1000Martin Sustrik
This patch is meant to prevent users from running out of memory when using 0MQ in the default configuration. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-09-03Fixed doc to clarify how label parts workPieter Hintjens
Signed-off-by: Pieter Hintjens <ph@imatix.com> Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-08-19Typo fixed in zmq_socket(3)Martin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-08-08ZMQ_IPV4ONLY option addedSteven McCoy
At this point option exists, is documented and can be set, however, it has no effect. Signed-off-by: Steven McCoy <steven.mccoy@miru.hk> Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-07-21ECANTROUTE error documented in zmq_sendmsg(3)Martin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-07-21ROUTER socket reports error when message cannot be routedMartin Sustrik
Till now, message was silently dropped if it was sent to a non-existent peer. Now, ECANTROUTE error is returned. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-07-18Reference to C++ binding removed from zmq(7)Martin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-07-18ZMQ_IDENTITY option removed from the documentationMartin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-07-11zmq_bind(3) and zmq_connect(3) describe EINVAL errorMartin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-07-11ZMQ_FILTER option removedMartin Sustrik
The filtering is now done depending on the socket type. SUB socket filters the messages (end-to-end filtering) while XSUB relies on upstream nodes to do (imprefect) filtering. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-07-11Man pages for send & recv function brought up to dateMartin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-06-26Typo in zmq_msg_size(3) fixedCarl Clemens
Signed-off-by: Carl Clemens <carlclemens1@yahoo.com>
2011-06-20Fix errors in zmq_getsockopt(3) manpageMartin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-06-20LABEL flag added to the wire formatMartin Sustrik
So far there was no distinction between message parts used by 0MQ and message parts used by user. Now, the message parts used by 0MQ are marked as 'LABEL'. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-06-19Documentation for XPUB and XSUB socket addedMartin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-06-17Add sockopt ZMQ_RCVTIMEO/ZMQ_SNDTIMEO.Fabien Ninoles
- Add doc and tests - Add options and setup - Wait using poll/select Signed-off-by: Fabien Ninoles <fabien@tzone.org> Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-06-12ZMQ_FILTER socket option addedMartin Sustrik
This option is a performance tweak. In devices XSUB socket filters the messages just to send them to XPUB socket which filters them once more. Setting ZMQ_FILTER option to 0 allows to switch the filtering in XSUB socket off. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-05-17zmq_msg_init_data returns ERRNO instead abortingPaul Colomiets
Signed-off-by: Paul Colomiets <pc@gafol.net>
2011-05-15ZMQ_MULTICAST_HOPS socket option addedMartin Sustrik
Sets the time-to-live field in every multicast packet sent from the socket. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-04-19Message validity is checked in the runtimeMartin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-04-18zmq_socket(3) describes the EMFILE error codeMartin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-04-15zmq_send(3) manpage improvedMartin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-04-11Fixed examplePieter Hintjens
Signed-off-by: Pieter Hintjens <ph@imatix.com>
2011-04-09Run-time checking for context & socket validity addedMartin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-04-03Add note about thread-safety to zmq_msg_init_data() manpage.Robert G. Jakabosky
Signed-off-by: Robert G. Jakabosky <bobby@sharedrealm.com>
2011-04-01PGM wire format specification improved in zmq_pgm(7)Martin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-03-26ZMQ_NOBLOCK renamed ZMQ_DONTWAITMartin Sustrik
Done because of POSIX compliance Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-03-24ZMQ_HWM split into ZMQ_SNDHWM and ZMQ_RCVHWMMartin Sustrik
These new options allow to control the maximum size of the inbound and outbound message pipe separately. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-03-24ZMQ_HWM type changed to intMartin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-03-24ZMQ_RATE and ZMQ_RECOVERY_IVL types cahnged to intMartin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-03-24ZMQ_EVENTS type changed to intMartin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-03-24ZMQ_RCVMORE type changed to intMartin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-03-24ZMQ_SNDBUF and ZMQ_RCVBUF type changed to intMartin Sustrik
This mimics POSIX specification. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-03-24ZMQ_RECOVERY_IVL and ZMQ_RECOVERY_IVL_MSEC reconciledMartin Sustrik
There's only one option now -- ZMQ_RECOVRY_IVL -- and it's measured in milliseconds. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-03-24SWAP functionality removedMartin Sustrik
On-disk storage should be implemented in devices rather than in 0MQ core. 0MQ is a networking library and there's no point in storing network buffers on disk. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-03-24C++ binding removed from the coreMartin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-03-23Pre-compiled devices removedMartin Sustrik
Along with the devices, xmlParser which is no longer needed is removed. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-03-23ZMQ_MCAST_LOOP removedMartin Sustrik
Multicast loopback is not a real multicast, rather a kernel-space simulation. Moreover, it tends to be rather unreliable and lossy. Removing the option will force users to use transports better suited for the job, such as inproc or ipc. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-03-23Timeout in zmq_poll is in millisecondsMartin Sustrik
The old timeout in microsecond haven't been compliant with POSIX and was impractical at the same time. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-03-23Obsolete note removed from zmq_poll(3) manpageMartin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-03-16zmq_socket(3) and zmq_setsockopt(3) man pages improvedMartin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-03-03Documentation wrt thread-safety cleaned up.Martin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-03-02ZMQ_MAXMSGSIZE option addedMartin Sustrik
The new option allows user to guard against peers sending oversized messages. Connection to peer sending oversized message is dropped. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-02-24Minor patch to zmq_getsockopt(3) man pageMartin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-02-15Added note regarding setting sockopt before bind/connectMichael Compton
Signed-off-by: Michael Compton <michael.compton@littleedge.co.uk>
2011-02-09Initial implementation of reaper thread.Martin Sustrik
Reaper thread destroys the socket asynchronously. zmq_term() can be interrupted by a signal (EINTR). zmq_socket() will return ETERM after zmq_term() was called. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2011-01-26ZMQ_RECONNECT_IVL_MAX socket option addedThijs Terlouw
It allows for exponential back-off strategy when reconnecting. Signed-off-by: Thijs Terlouw <thijsterlouw@gmail.com>
2011-01-17Typo fixed in zmq_send(3) man page.Martin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2010-12-09Added Recovery Interval in MillisecondsBob 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>