1. 30 Mar, 2016 2 commits
  2. 29 Mar, 2016 2 commits
  3. 18 Feb, 2016 1 commit
  4. 11 Feb, 2016 2 commits
    • Pieter Hintjens's avatar
      Problem: tweetnacl sources are a mess · f8ed793f
      Pieter Hintjens authored
      - they have no copyright / license statement
      - they are in some randomish directory structure
      - they are a mix of postable and non-portable files
      - they do not conform to conditional compile environment
      
      Overall, it makes it rather more work than needed, in build scripts.
      
      Solution: clean up tweetnacl sauce.
      
      - merged code into single tweetnacl.c and .h
      - standard copyright header, DJB to AUTHORS
      - moved into src/ along with all other source files
      - all system and conditional compilation hidden in these files
      - thus, they can be compiled and packaged in all cases
      - ZMQ_USE_TWEETNACL is set when we're using built-in tweetnacl
      - HAVE_LIBSODIUM is set when we're using external libsodium
      f8ed793f
    • Pieter Hintjens's avatar
      Problem: use of libsodium vs. tweetnacl is confused · b49a6041
      Pieter Hintjens authored
      It's unclear which we need and in the source code, conditional code
      treats tweetnacl as a subclass of libsodium, which is inaccurate.
      
      Solution: redesign the configure/cmake API for this:
      
      * tweetnacl is present by default and cannot be enabled
      * libsodium can be enabled using --with-libsodium, which replaces
        the built-in tweetnacl
      * CURVE encryption can be disabled entirely using --enable-curve=no
      
      The macros we define in platform.hpp are:
      
          ZMQ_HAVE_CURVE    1        //  When CURVE is enabled
          HAVE_LIBSODIUM    1        //  When we are using libsodium
          HAVE_TWEETNACL    1        //  When we're using tweetnacl (default)
      
      As of this patch, the default build of libzmq always has CURVE
      security, and always uses tweetnacl.
      b49a6041
  5. 09 Feb, 2016 1 commit
    • Pieter Hintjens's avatar
      Problem: test_large_msg kills my system temporarily · 62c66ae7
      Pieter Hintjens authored
      And I'm on a reasonably sized laptop. I think allocating INT_MAX
      memory is dangerous in a test case.
      
      Solution: expose this as a context option. I've used ZMQ_MAX_MSGSZ
      and documented it and implemented the API. However I don't know how
      to get the parent context for a socket, so the code in zmq.cpp is
      still unfinished.
      62c66ae7
  6. 01 Feb, 2016 3 commits
  7. 28 Jan, 2016 1 commit
  8. 08 Dec, 2015 1 commit
    • Ilya Kulakov's avatar
      Add the VMCI transport. · 68b13fbd
      Ilya Kulakov authored
      VMCI transport allows fast communication between the Host
      and a virtual machine, between virtual machines on the same host,
      and within a virtual machine (like IPC).
      
      It requires VMware to be installed on the host and Guest Additions
      to be installed on a guest.
      68b13fbd
  9. 21 Aug, 2015 2 commits
  10. 16 Aug, 2015 1 commit
  11. 05 Jun, 2015 1 commit
  12. 02 Jun, 2015 1 commit
  13. 12 Feb, 2015 1 commit
  14. 22 Jan, 2015 1 commit
  15. 17 Nov, 2014 1 commit
  16. 31 Aug, 2014 1 commit
  17. 09 Jul, 2014 2 commits
  18. 02 Jul, 2014 1 commit
  19. 11 Jun, 2014 1 commit
  20. 04 Jun, 2014 1 commit
  21. 23 May, 2014 1 commit
  22. 22 May, 2014 1 commit
  23. 21 May, 2014 1 commit
    • Martin Hurton's avatar
      Code cleanup · 414fc86b
      Martin Hurton authored
      - limit visibility of pending_connection_t
      - add const qualifiers
      414fc86b
  24. 16 May, 2014 1 commit
  25. 14 Feb, 2014 1 commit
  26. 13 Feb, 2014 1 commit
    • Olaf Mandel's avatar
      Add ZMQ_MAX_SOCKETS_MAX to zmq_ctx_get() · 5815b768
      Olaf Mandel authored
      The new options allows querying the maximum allowed number of sockets.
      This is system dependent and cannot be encoded in the include file as a
      preprocessor macro: for ZMQ_USE_SELECT, this depends on the FD_SETSIZE
      macro at time of library compilation, not at time of include file use.
      5815b768
  27. 12 Feb, 2014 2 commits
  28. 09 Feb, 2014 1 commit
  29. 03 Feb, 2014 1 commit
  30. 02 Jan, 2014 1 commit
  31. 07 Nov, 2013 2 commits