1. 23 Jul, 2015 4 commits
  2. 22 Jul, 2015 4 commits
  3. 20 Jul, 2015 1 commit
  4. 08 Jul, 2015 1 commit
  5. 07 Jul, 2015 2 commits
  6. 05 Jul, 2015 4 commits
  7. 02 Jul, 2015 1 commit
  8. 01 Jul, 2015 2 commits
  9. 30 Jun, 2015 3 commits
  10. 26 Jun, 2015 1 commit
    • Jonathan Reams's avatar
      Fix units and default values for heartbeats options · e9a5bc8d
      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)
      e9a5bc8d
  11. 24 Jun, 2015 1 commit
  12. 23 Jun, 2015 2 commits
  13. 14 Jun, 2015 3 commits
    • Jens Auer's avatar
      Reuse buffer when no messages depend on it. · e70b5efa
      Jens Auer authored
      e70b5efa
    • Jens Auer's avatar
      Fixed wrong handling of shared messages · 51cb57e2
      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.
      51cb57e2
    • Jens Auer's avatar
      Fixed wrong buffer end detection in v2_decoder. · dfe19080
      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.
      dfe19080
  14. 13 Jun, 2015 1 commit
  15. 07 Jun, 2015 2 commits
  16. 05 Jun, 2015 3 commits
  17. 03 Jun, 2015 2 commits
    • Jens Auer's avatar
      zero-copy message receive · e9b403a7
      Jens Auer authored
      Construct messages from a reference-counted buffer allocated once
      per receive instead of copying the data.
      e9b403a7
    • Jens Auer's avatar
      Allocation-free msg::init_data · 611e96c7
      Jens Auer authored
      With a msg_t size of 64 bytes, it becomes possible to embedd the content_t's members
      struct for large messages directly in the msg_t. This saves the dynamic allocation
      of content_t obejcts when using msg_t::init_data.
      
      content_t contains a zmq::atomic_counter_t object which is not a POD in C++98
      and thus it cannot be used as a member of the union u. To bypass this, C++11
      is used which has relaxed rules for POD and atomic_counter is a C++11-POD. An
      alternative would have been to make atomic_counter a classical POD by removing
      constructors and all private member functions, i.e. have a struct and free functions
      to manipulate it.
      
      A new msg_t::init function is added which decides to either to copy the data for size<64 bytes
      or use msg_t::init_data to do zero-copy initialization.
      611e96c7
  18. 02 Jun, 2015 2 commits
  19. 27 May, 2015 1 commit