1. 26 Jul, 2018 1 commit
  2. 29 May, 2018 5 commits
  3. 27 May, 2018 1 commit
  4. 18 May, 2018 1 commit
  5. 06 Mar, 2018 1 commit
  6. 02 Feb, 2018 1 commit
  7. 21 Oct, 2017 1 commit
  8. 19 Sep, 2017 2 commits
  9. 07 Sep, 2017 2 commits
  10. 06 Sep, 2017 1 commit
  11. 17 Sep, 2016 1 commit
  12. 18 Feb, 2016 1 commit
  13. 07 Feb, 2016 1 commit
  14. 06 Feb, 2016 1 commit
  15. 05 Feb, 2016 1 commit
  16. 28 Jan, 2016 1 commit
  17. 06 Sep, 2015 1 commit
  18. 21 Aug, 2015 2 commits
  19. 14 Aug, 2015 1 commit
  20. 22 Jul, 2015 1 commit
  21. 02 Jun, 2015 1 commit
  22. 22 Apr, 2015 1 commit
  23. 19 Feb, 2015 1 commit
  24. 18 Feb, 2015 1 commit
  25. 11 Feb, 2015 1 commit
  26. 23 Jan, 2015 1 commit
    • Pieter Hintjens's avatar
      Problem: commit afb24b53 broke ZMQ_STREAM contract · 6ced7027
      Pieter Hintjens authored
      Symptom is that ZMQ_STREAM sockets in 4.1.0 and 4.1.1 generate zero
      sized messages on each new connection, unlike 4.0.x which did not do
      this.
      
      Person who made this commit also changed test cases so that contract
      breakage did not show. Same person was later banned for persistently
      poor form in CZMQ contributions.
      
      Solution: enable connect notifications on ZMQ_STREAM sockets using a
      new ZMQ_STREAM_NOTIFY setting. By default, socket does not deliver
      notifications, and behaves as in 4.0.x.
      
      Fixes #1316
      6ced7027
  27. 22 Jan, 2015 1 commit
  28. 21 Jan, 2014 1 commit
  29. 20 Jan, 2014 1 commit
  30. 19 Jan, 2014 3 commits
  31. 18 Jan, 2014 1 commit