1. 27 Jan, 2020 1 commit
  2. 27 May, 2018 1 commit
  3. 26 May, 2018 2 commits
  4. 02 Feb, 2018 1 commit
  5. 19 Sep, 2017 1 commit
  6. 07 Sep, 2017 2 commits
  7. 18 Feb, 2016 1 commit
  8. 28 Jan, 2016 1 commit
  9. 02 Jun, 2015 1 commit
  10. 27 Jan, 2015 1 commit
    • Thomas Rodgers's avatar
      Clean up of metadata_t · 1c72bf4e
      Thomas Rodgers authored
      * There is no clear reason why the map should hold const std::strings
      * This class is never derived, there doesn't seem to be a compelling
        reason to ever do so, so no need to make virtual members
      * In general const member data is an anti-pattern, the *only* reason
        is to prevent assignability, and the accepted idiom for that is to
        to declare the assigment operator private. This change does so, and
        also prevents copy construction.
      1c72bf4e
  11. 22 Jan, 2015 1 commit
  12. 02 May, 2014 1 commit
  13. 01 May, 2014 1 commit
  14. 02 Jan, 2014 1 commit
  15. 29 Jun, 2013 2 commits
  16. 12 Mar, 2013 1 commit
    • Pieter Hintjens's avatar
      Removed corporate advertisements from source file headers · f0f16505
      Pieter Hintjens authored
      Copyrights had become ads for Sustrik's corporate sponsors, going against the original
      agreement to share copyrights with the community (that agreement was: one line stating
      iMatix copyright + one reference to AUTHORS file). The proliferation of corporate ads
      is also unfair to the many individual authors. I've removed ALL corporate title from
      the source files so the copyright statements can now be centralized in AUTHORS and
      source files can be properly updated on an annual basis.
      f0f16505
  17. 09 Nov, 2012 1 commit
  18. 27 Aug, 2012 1 commit
    • Arthur O'Dwyer's avatar
      Silence all "unused parameter" warnings from Clang. · 3b984d40
      Arthur O'Dwyer authored
      Compiling without warnings is a good goal, because it makes
      new warnings (which probably indicate bugs) stand out rather
      than getting lost in the spam.
      
      My fixes fall into two categories:
      
          - Adding (void) casts of unused parameters, where their
            unusedness seems like a TODO (or in some cases a bug?).
      
          - Removing parameter names altogether, where the function
            is clearly a stub that will never use its parameters.
      
      Should be no change in behavior.
      3b984d40
  19. 20 Mar, 2012 1 commit
    • Pieter Hintjens's avatar
      Fixed issues #337, #341, and #340 · 6e71a54b
      Pieter Hintjens authored
      * Implemented new ctx API (_new, _destroy, _get, _set)
      * Removed 'typesafe' macros from zmq.h
      * Added support for MAX_SOCKETS (was tied into change for #337)
      * Created new man pages
      6e71a54b
  20. 16 Feb, 2012 1 commit
  21. 15 Feb, 2012 1 commit
  22. 10 Feb, 2012 1 commit
  23. 01 Nov, 2011 1 commit
  24. 31 Oct, 2011 1 commit
  25. 15 Sep, 2011 1 commit
  26. 30 May, 2011 1 commit
  27. 21 Apr, 2011 1 commit
  28. 02 Mar, 2011 1 commit
  29. 06 Dec, 2010 1 commit
  30. 04 Dec, 2010 1 commit
  31. 05 Nov, 2010 1 commit
  32. 30 Oct, 2010 1 commit
  33. 16 Oct, 2010 1 commit
    • Martin Sustrik's avatar
      ZMQ_LINGER socket option added. · 0a03e86e
      Martin Sustrik authored
          1. ZMQ_LINGER option can be set/get
          2. options are part of own_t base class rather than being declared
             separately by individual objects
          3. Linger option is propagated with "term" command so that the
             newest value of it is used rather than the stored old one.
          4. Session sets the linger timer if needed and terminates
             as soon as it expires.
          5. Corresponding documentation updated.
      Signed-off-by: 's avatarMartin Sustrik <sustrik@250bpm.com>
      0a03e86e
  34. 28 Sep, 2010 1 commit
  35. 01 Sep, 2010 1 commit
  36. 25 Aug, 2010 2 commits
    • Martin Sustrik's avatar
      I/O object hierarchy implemented · d13933bc
      Martin Sustrik authored
      d13933bc
    • Martin Sustrik's avatar
      WIP: Socket migration between threads, new zmq_close() semantics · 05d90849
      Martin Sustrik authored
      Sockets may now be migrated between OS threads; sockets may not be used by
      more than one thread at any time. To migrate a socket to another thread the
      caller must ensure that a full memory barrier is called before using the
      socket from the target thread.
      
      The new zmq_close() semantics implement the behaviour discussed at:
      
      http://lists.zeromq.org/pipermail/zeromq-dev/2010-July/004244.html
      
      Specifically, zmq_close() is now deterministic and while it still returns
      immediately, it does not discard any data that may still be queued for
      sending. Further, zmq_term() will now block until all outstanding data has
      been sent.
      
      TODO: Many bugs have been introduced, needs testing. Further, SO_LINGER or
      an equivalent mechanism (possibly a configurable timeout to zmq_term())
      needs to be implemented.
      05d90849