- 26 Jun, 2015 1 commit
-
-
Jonathan Reams authored
Set the ZMQ_HEARTBEAT_TIMEOUT to default to the value of ZMQ_HEARTBEAT_IVL if it's not explicitly set. Change the units of ZMQ_HEARTBEAT_TTL to milliseconds in the API and round down to the nearest decisecond so that all the options are using the same units. Make the maximum heartbeat TTL match the spec (6553 seconds)
-
- 24 Jun, 2015 5 commits
-
-
Pieter Hintjens authored
Add documentation for ZMTP heartbeats/fix test
-
Jonathan Reams authored
-
Jonathan Reams authored
-
Pieter Hintjens authored
Add ZMTP connection heartbeats
-
Jonathan Reams authored
This commit adds ZMTP connection heartbeats described in http://rfc.zeromq.org/spec:37/ZMTP.
-
- 23 Jun, 2015 4 commits
-
-
Constantin Rack authored
Typo fix
-
Marin Atanasov Nikolov authored
-
Richard Newton authored
Problem: zmq::socket_base_t::connect fails on tcp ipv6 address
-
Constantin Rack authored
-
- 14 Jun, 2015 4 commits
-
-
Pieter Hintjens authored
Rebase3
-
Jens Auer authored
-
Jens Auer authored
The shared reference count was not shared but copied. msg_t cannot store the refcnt itsef but has to store a pointer to an externally allocated (shared) refcnter. The changes to lmsg are reverted to use content_t again. Howver, this introduces an allocation in v2_decoder when creating the message which can be avoided. When allocating the reception buffer, space is allocated for the maximum number of reference counts (8192 / max_vsm_size = 8192/64 = 128 zmq:atomic_counter objects). This increases the buffer by 128*sizeof(atomic_counter) = 128*4 = 512 bytes only. When creating a message, the refcnt member is set to the address of one of the pre-allocated atomic_counter_t objects. To do so, a new msg_t type zcmsg is introduced because msg::copy must discriminate between the message types when releasing memory.
-
Jens Auer authored
zero-copy msg_t::init cannot be used when the message exceeds either the buffer end or the last received byte. To detect this, the buffer is now resized to the numnber of received bytes.
-
- 13 Jun, 2015 2 commits
-
-
Constantin Rack authored
Probably fix build issue on Solaris.
-
Kapp Arnaud authored
See #1220 recent comments. This change is untested yet seems safe.
-
- 11 Jun, 2015 2 commits
-
-
KAPP Arnaud authored
Problem: 4.1 broke the ABI yet did not bump ABI number
-
Pieter Hintjens authored
Solution: bump to ABI version 5
-
- 10 Jun, 2015 3 commits
-
-
Pieter Hintjens authored
Fix windows build
-
Richard Newton authored
-
Richard Newton authored
-
- 08 Jun, 2015 2 commits
-
-
Pieter Hintjens authored
test zmq_msg custom free-function
-
Min RK authored
new allocation caused reference counters to lose track on copy
-
- 07 Jun, 2015 5 commits
-
-
Pieter Hintjens authored
don't check POLLOUT for single-socket proxies
-
Min RK authored
-
Min RK authored
-
Thomas Rodgers authored
Fix initialization order.
-
Kapp Arnaud authored
Fixes #1431.
-
- 06 Jun, 2015 2 commits
-
-
KAPP Arnaud authored
Enable install of man pages when BUILD_DOC is not set by shifting INS…
-
Jason Unovitch authored
Enable install of man pages when BUILD_DOC is not set by shifting INSTALL_MAN outside of BUILD_DOC's if/endif
-
- 05 Jun, 2015 10 commits
-
-
Pieter Hintjens authored
Update documentation for zmq_setsockopt.
-
Kapp Arnaud authored
Pull request #1426 now allow for changing the watermark after and connect() or a bind(). This patch reflect the change in the documentation. Also closes #1416.
-
Constantin Rack authored
Allow changing of high water marks after connection is established
-
Richard Newton authored
-
Richard Newton authored
-
KAPP Arnaud authored
Fixed executable name in the usage string
-
Mipa authored
-
Constantin Rack authored
Fix xpub test to set hwm before bind.
-
Richard Newton authored
-
Pieter Hintjens authored
Fail ZMQ_SNDHWM and ZMQ_RCVHWM setsockopt if already connected.
-