- 18 Oct, 2015 1 commit
-
-
somdoron authored
-
- 13 Sep, 2015 1 commit
-
-
Pieter Hintjens authored
These sockets deal only with single part data (at present), so the drop tests are misleading / inappropriate. Solution: remove them.
-
- 16 Aug, 2015 1 commit
-
-
somdoron authored
-
- 13 Aug, 2015 1 commit
-
-
sappo authored
Solution: Add prefix to fix test compilation
-
- 11 Aug, 2015 2 commits
-
-
Rik van der Heijden authored
-
Pieter Hintjens authored
Solution: specify the necessary EXTRA_DIST I added a Makefile.am in builds that covers all systems except msvc, which already has a Makefile.am that does this. Fixes #1505
-
- 20 Jul, 2015 2 commits
- 05 Jul, 2015 1 commit
-
-
Jens Auer authored
A memcpy is eliminated when receiving data on a ZMQ_STREAM socket. Instead of receiving into a static buffer and then copying the data into the buffer malloced in msg_t::init_size, the raw_decoder allocates the memory for together with the reference-counter and creates a msg_t object on top of that memory. This saves the memcpy operation. For small messages, data is still copied and the receive buffer is reused.
-
- 29 Jun, 2015 1 commit
-
-
Dylan Cali authored
-
- 24 Jun, 2015 1 commit
-
-
Jonathan Reams authored
This commit adds ZMTP connection heartbeats described in http://rfc.zeromq.org/spec:37/ZMTP.
-
- 14 Jun, 2015 1 commit
-
-
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.
-
- 08 Jun, 2015 1 commit
-
-
Min RK authored
new allocation caused reference counters to lose track on copy
-
- 07 Jun, 2015 1 commit
-
-
Min RK authored
-
- 05 Jun, 2015 1 commit
-
-
Richard Newton authored
-
- 04 Jun, 2015 1 commit
-
-
Pieter Hintjens authored
Solution: mark this as XFAIL
-
- 03 Jun, 2015 1 commit
-
-
Kapp Arnaud authored
Problem: zmq_setsockpt() returns success when changing the HWM after a bind or connect() even though the call has no effect. Solution: Introduce a failing test a reminder we need to patch it.
-
- 01 May, 2015 2 commits
-
-
Pieter Hintjens authored
Solution: fixed this in Makefile.am
-
Rik van der Heijden authored
-
- 18 Feb, 2015 1 commit
-
-
Thomas Rodgers authored
-
- 12 Feb, 2015 1 commit
-
-
somdoron authored
-
- 07 Feb, 2015 2 commits
-
-
Florian Ebeling authored
-
Florian Ebeling authored
-
- 02 Feb, 2015 3 commits
- 01 Feb, 2015 1 commit
-
-
somdoron authored
-
- 21 Jan, 2015 1 commit
-
-
Thomas Rodgers authored
-
- 09 Jan, 2015 1 commit
-
-
Thomas Rodgers authored
Revert "linking fd to pipe identity via socket option" This reverts commit fe3e8c5c. Conflicts: include/zmq.h src/pipe.hpp src/session_base.cpp
-
- 29 Dec, 2014 1 commit
-
-
DaiyuHurst authored
-
- 23 Dec, 2014 1 commit
-
-
Pieter Hintjens authored
Solution: as libzmq already provides this across all platforms, expose an atomic counter API. I've not wrapped atomic pointers, though someone who needs this may want to do so.
-
- 26 Nov, 2014 2 commits
- 03 Nov, 2014 1 commit
-
-
Phillip Mienk authored
-
- 17 Oct, 2014 1 commit
-
-
J.T. Conklin authored
-
- 16 Oct, 2014 1 commit
-
-
Phillip Mienk authored
-
- 14 Oct, 2014 1 commit
-
-
Phillip Mienk authored
-
- 10 Oct, 2014 1 commit
-
-
Phillip Mienk authored
-
- 23 Oct, 2013 1 commit
-
-
xantares authored
-
- 28 Jun, 2013 1 commit
-
-
Pieter Hintjens authored
The use of binary for CURVE keys is painful; you cannot easily copy these in e.g. email, or use them directly in source code. There are various encoding possibilities. Base16 and Base64 are not optimal. Ascii85 is not safe for source (it generates quotes and escapes). So, I've designed a new Base85 encoding, Z85, which is safe to use in code and elsewhere, and I've modified libzmq to use this where it also uses binary keys (in get/setsockopt). Very simply, if you use a 32-byte value, it's Base256 (binary), and if you use a 40-byte value, it's Base85 (Z85). I've put the Z85 codec into z85_codec.hpp, it's not elegant C++ but it is minimal and it works. Feel free to rewrap as a real class if this annoys you.
-