1. 09 May, 2019 2 commits
  2. 28 Apr, 2019 1 commit
  3. 23 Feb, 2019 1 commit
  4. 09 Aug, 2018 1 commit
  5. 01 Jun, 2018 4 commits
  6. 27 May, 2018 2 commits
  7. 26 May, 2018 1 commit
  8. 18 May, 2018 1 commit
  9. 14 May, 2018 2 commits
  10. 28 Mar, 2018 1 commit
  11. 10 Mar, 2018 1 commit
    • Manuel Segura's avatar
      Pull request to merge porting to WindRiver VxWorks 6.x (#2966) · 4726f726
      Manuel Segura authored
      * Problem: Still need to port over more files to VxWorks 6.x
      
      Solution: Port more files to VxWorks 6.x
      
      * Problem: Need to port over remaining files to VxWorks 6.x. Also remove POSIX thread dependency for VxWorks (because of priority inversion problem in POSIX mutexes with VxWorks 6.x processes)
      
      Solution: Port over remaining files to VxWorks 6.x. Also removed POSIX thread dependency for VxWorks
      
      * Problem: Needed to modify TCP, UDP, TIPC classes with #ifdefs to be compatible with VxWorks 6.x.
      
      Solution:  Modify TCP, UDP, TIPC classes with #ifdefs to be compatible with VxWorks 6.x
      4726f726
  12. 08 Feb, 2018 2 commits
  13. 02 Feb, 2018 1 commit
  14. 31 Jan, 2018 1 commit
  15. 02 Nov, 2017 1 commit
  16. 12 Sep, 2017 1 commit
    • Marc Sune's avatar
      Problem: duplicated socket_poller::wait() code · 5b929895
      Marc Sune authored
      zmq::socket_poller_t::wait() had an important set of common lines
      between POLL and SELECT variant.
      
      Solution: refactor zmq::socket_poller_t::wait() and add the
      following methods:
      
      zmq::socket_poller_t::zero_trail_events()
      zmq::socket_poller_t::check_events()
      zmq::socket_poller_t::adjust_timeout()
      Signed-off-by: 's avatarMarc Sune <mardevel@gmail.com>
      5b929895
  17. 22 Aug, 2017 3 commits
  18. 10 Apr, 2017 2 commits
  19. 11 Mar, 2017 1 commit
  20. 29 Sep, 2016 1 commit
    • Min RK's avatar
      socket_poller::wait returns only triggered events · 718608ce
      Min RK authored
      Return value is the number of events found. This also propagates to the return value of zmq_poller_wait_all.
      
      zmq_poller_wait was only returning events on the first-registered socket.
      718608ce
  21. 28 Sep, 2016 1 commit
  22. 27 Sep, 2016 2 commits
    • Min RK's avatar
      add n_events argument to zmq_poller_wait_all · de7fc1fc
      Min RK authored
      avoids unnecessary heap allocations, races on the number of items
      de7fc1fc
    • Min RK's avatar
      Problem: zmq_poller only signals one event · 2bc97966
      Min RK authored
      Solution: zmq_poller_wait_all signals all events
      
      allows signaling multiple events with one call to zmq_poller_wait_all
      rather than emitting only one event.
      
      this prepares for zmq_poll being based on zmq_poller,
      which requires events for all sockets rather than just one.
      2bc97966
  23. 05 May, 2016 1 commit
  24. 13 Apr, 2016 2 commits
  25. 12 Apr, 2016 1 commit
    • Patrik Wenger's avatar
      Problem: tricky return value from zmq::socket_poller_t::wait when poller is empty · 621c965f
      Patrik Wenger authored
      Solution: return -1 (no event) instead of 0 (event)
      
      For some reason, this just returns 0 if there are no sockets registered
      on the poller. Usually this would mean there has been an event. So the
      caller would have to check the return value AND the event, or write code
      that takes the number of registered sockets into consideration.
      
      By returning -1 and setting errno = ETIMEDOUT like in the usual timeout
      cases, it's more consistent and convenient.
      
      Test case included.
      621c965f
  26. 21 Feb, 2016 3 commits