summaryrefslogtreecommitdiff
path: root/doc/zmq_setsockopt.txt
AgeCommit message (Collapse)Author
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_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-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-16zmq_socket(3) and zmq_setsockopt(3) man pages improvedMartin 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-15Added note regarding setting sockopt before bind/connectMichael Compton
Signed-off-by: Michael Compton <michael.compton@littleedge.co.uk>
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>
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>
2010-12-01Documentation updates for 2.1Martin Lucina
- Clarify ZMQ_LINGER, zmq_close (), zmq_term () relationship - New socket options - Clarify thread safety of sockets and migration between threads - Other minor and spelling fixes Signed-off-by: Martin Lucina <mato@kotelna.sk>
2010-11-04Fix documentation typosJacob Rideout
Signed-off-by: Jacob Rideout <jacob.rideout@returnpath.net>
2010-10-17ZMQ_BACKLOG socket option added.Martin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2010-10-17ZMQ_RECONNECT_IVL socket options added.Martin Sustrik
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
2010-10-16ZMQ_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-08EINTR returned from the blocking functionsMartin Sustrik
2010-09-04Revert "Various changes to documentation project:"Martin Lucina
This reverts commit 77a3c36ff1f11215229a4efdb821a3cb83a9d6fc.
2010-09-04Revert "Further cleanups on reference manual"Martin Lucina
This reverts commit 13f3481e127a6b2390e847af6b01ee88f1b4ae61. Conflicts: doc/zmq_device.txt doc/zmq_tcp.txt
2010-08-11Fixed (un)signed type errors in get/setsockopt manualPieter Hintjens
2010-08-08Added error checking (EFAULT) for null argumentsPieter Hintjens
* Fixed zmq_term, zmq_socket, zmq_close, zmq_setsockopt, * zmq_getsockopt, zmq_bind, zmq_connect, zmq_send, * zmq_recv, zmq_poll, zmq_device, zmq_stopwatch_stop * Updated Reference Manual for these methods
2010-08-04Further cleanups on reference manualPieter Hintjens
- fixed unwrapped text in new man pages - fixed over-long lines in older pages, where possible - removed reference to old standalong devices from index page - added refernce to new zmq_device[3] documented from index page - some minor spelling corrections
2010-08-04Various changes to documentation project:Pieter Hintjens
* Added documentation for zmq_deviced, which we're developing * Created consistent page footer in documentation template * Page footer notes doc authors and copyright statement
2010-06-03Documentation: Cosmetic changesMartin Lucina
2010-06-02Documentation: Flow control, zmq_socket(3)Martin Lucina
Mostly Flow control and additions to zmq_socket(3) Removed/changed lots of text regarding message queues More fixes for 2.0.7 changes
2010-06-01Documentation: zmq_term() and ETERM for 2.0.7Martin Lucina
2010-05-31Documentation updatesMartin Lucina
Add zmq_getsockopt(3), clean up zmq_setsockopt(3).
2010-05-28Clarify socket types in documentation, reinstate ZMQ_PAIRMartin Lucina
2010-05-25LWM is computed rather than explicitly specified by userMartin Sustrik
2010-04-16fix of documentation typoMartin Sustrik
2010-04-12ETERM is accounted for in the documentationMartin Sustrik
2010-04-06Documentation fixesMartin Lucina
2010-03-10Documentation fixesMartin Lucina
2010-03-09Documentation rewriteMartin Lucina
2010-02-19Multi-hop REQ/REP, part XII., generate unique identities for anonymous ↵Martin Sustrik
connections
2010-02-10Convert documentation to AsciiDocMartin Lucina