- 09 Apr, 2020 1 commit
-
-
Gudmundur Adalsteinsson authored
* Problem: boilerplate when init msg from data copy Solution: Add zmq_msg_init_buffer to construct a message by copying memory from buffer.
-
- 07 Mar, 2020 1 commit
-
-
Luca Boccassi authored
Solution: fix them
-
- 09 Feb, 2020 1 commit
-
-
Doron Somech authored
-
- 05 Feb, 2020 1 commit
-
-
Luca Boccassi authored
Solution: if all peers of a socket are >= 3.1 use sub/cancel commands instead of the old 0/1 messages. For backward compatibility, move the handling of 0/1 or sub/cancel command strings to the encoders, so that the right thing can be done depending on the protocol version. Do not set the command flag until the encoder, so that we can handle the inproc case (which skips the encoder).
-
- 03 Feb, 2020 1 commit
-
-
Simon Giesecke authored
Solution: use crypto_box_easy_afternm and crypto_box_open_easy_afternm in-place
-
- 27 Jan, 2020 2 commits
-
-
Simon Giesecke authored
Solution: add const/static
-
Simon Giesecke authored
Solution: add const
-
- 18 Jan, 2020 1 commit
-
-
Doron Somech authored
Solution: when peer send a close msg, close the connection
-
- 23 Jun, 2018 1 commit
-
-
Luca Boccassi authored
Solution: add some msg helpers to parse commands, and check for subscribe or cancel commands and process them accordingly in the xpub and xsub classes.
-
- 30 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: remove redundant else
-
- 28 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: extract constants and unified cases
-
- 27 May, 2018 1 commit
-
-
Simon Giesecke authored
Problem: inconsistent naming style for private data members, conflicts with naming of local variables and member functions Solution: apply and check _lower_case naming style for private data members
-
- 26 May, 2018 2 commits
-
-
Simon Giesecke authored
Solution: remove else
-
Simon Giesecke authored
Solution: define and apply parameter naming style: lower_case_
-
- 18 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: replace by C++-style casts
-
- 27 Feb, 2018 1 commit
-
-
Romain Geissler authored
-
- 02 Feb, 2018 1 commit
-
-
sigiesec authored
Solution: applied clang-format
-
- 19 Sep, 2017 1 commit
-
-
sigiesec authored
Solution: replace by "routing id"
-
- 07 Sep, 2017 1 commit
-
-
Doron Somech authored
-
- 06 Sep, 2017 1 commit
-
-
sigiesec authored
Solution: replace by "routing id"
-
- 30 Mar, 2017 1 commit
-
-
evoskuil authored
-
- 26 Mar, 2017 1 commit
-
-
evoskuil authored
-
- 14 May, 2016 1 commit
-
-
evoskuil authored
-
- 04 May, 2016 1 commit
-
-
Doron Somech authored
-
- 18 Feb, 2016 1 commit
-
-
Osiris authored
Solution: Phase I - make precompiled.hpp be first file included in every source file
-
- 29 Jan, 2016 4 commits
- 28 Jan, 2016 2 commits
-
-
somdoron authored
-
Constantin Rack authored
Solution: update to 2016
-
- 19 Jan, 2016 1 commit
-
-
somdoron authored
-
- 11 Sep, 2015 2 commits
-
-
Pieter Hintjens authored
Solution: check/reject a zero routing ID with EINVAL.
-
Pieter Hintjens authored
We do not use 'get' for getters. Solution: rename to zmq_msg_routing_id () for public API.
-
- 21 Aug, 2015 1 commit
-
-
Joe Eli McIlvain authored
Solution: Move the macros to a private header.
-
- 17 Aug, 2015 1 commit
-
-
Constantin Rack authored
-
- 16 Aug, 2015 1 commit
-
-
reza.ebrahimi authored
-
- 25 Jul, 2015 1 commit
-
-
KIU Shueng Chuan authored
-
- 07 Jul, 2015 1 commit
-
-
Juha Reunanen authored
-
- 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.
-