1. 16 Jun, 2016 1 commit
  2. 13 Jun, 2016 1 commit
    • Armin Burgmeier's avatar
      Flush stderr buffer before calling zmq_abort in assert macros · 07a37435
      Armin Burgmeier authored
      On Windows, the written message does not seem to be guaranteed to be
      written to stderr, in particular when stderr is redirected to a file. I
      suppose this is because RaiseException terminates the process in a way
      that does not give the CRT a chance to flush stdio buffers (or if it
      does, there might be a problem when more than one CRT instance is linked
      into the program and they overwrite each other's exception handler). Either
      way, just make sure the assertion message ends up written to stderr to
      ease diagnostics.
      07a37435
  3. 11 Jun, 2016 2 commits
    • Michael Lutz's avatar
      Problem: Windows performance is not optimal due to select(). · 7a6ff07a
      Michael Lutz authored
      Solution: Provide poll() for Windows as well. This is a build option that
      defaults to off as the resulting binary will only run on Windows Vista or
      newer.
      
      This is not tested with alternative Winsock service providers like VMCI,
      but the documentation for WSAPoll does not mention limitations.
      
      On my local machine, throughput improves by ~10 % (20 simultaneous
      remote_thr workes to one local_thr, 10 byte messages), while latency
      improves by ~30 % (measured with remote/local_lat).
      7a6ff07a
    • Michael Lutz's avatar
      Problem: Theoretical overflow when polling more than INT_MAX handles. · 8d8d32f4
      Michael Lutz authored
      Solution: Always use fd_t when accessing the pollset.
      8d8d32f4
  4. 09 Jun, 2016 2 commits
  5. 01 Jun, 2016 1 commit
  6. 27 May, 2016 2 commits
  7. 20 May, 2016 1 commit
  8. 19 May, 2016 2 commits
  9. 18 May, 2016 2 commits
  10. 16 May, 2016 8 commits
  11. 15 May, 2016 4 commits
  12. 14 May, 2016 1 commit
  13. 13 May, 2016 1 commit
  14. 12 May, 2016 3 commits
  15. 11 May, 2016 1 commit
    • Erik Hugne's avatar
      tipc: add support for address domain suffix · f81ef1bc
      Erik Hugne authored
      The TIPC protocol bindings in ZeroMQ defaults to a lookup domain
      of 1.0.0 to prevent 'closest first' search, and instead always
      do round robin if several sockets in the network or node have
      the same name published. In retrospect, this might have been a
      bad idea because it won't work on standalone configurations.
      We solve this by allowing an optional domain suffix to be provided
      in the address, and 0.0.0 should be used in that case, or if the
      TIPC address range in the cluster configuration is defined to some
      other value. Domain suffixes are only relevant for connecting
      addresses.
      Signed-off-by: 's avatarErik Hugne <erik.hugne@gmail.com>
      f81ef1bc
  16. 10 May, 2016 4 commits
  17. 08 May, 2016 2 commits
  18. 06 May, 2016 1 commit
  19. 05 May, 2016 1 commit