1. 06 Mar, 2018 1 commit
  2. 02 Feb, 2018 1 commit
  3. 21 Oct, 2017 1 commit
  4. 19 Sep, 2017 2 commits
  5. 07 Sep, 2017 2 commits
  6. 06 Sep, 2017 1 commit
  7. 17 Sep, 2016 1 commit
  8. 18 Feb, 2016 1 commit
  9. 07 Feb, 2016 1 commit
  10. 06 Feb, 2016 1 commit
  11. 05 Feb, 2016 1 commit
  12. 28 Jan, 2016 1 commit
  13. 06 Sep, 2015 1 commit
  14. 21 Aug, 2015 2 commits
  15. 14 Aug, 2015 1 commit
  16. 22 Jul, 2015 1 commit
  17. 02 Jun, 2015 1 commit
  18. 22 Apr, 2015 1 commit
  19. 19 Feb, 2015 1 commit
  20. 18 Feb, 2015 1 commit
  21. 11 Feb, 2015 1 commit
  22. 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
  23. 22 Jan, 2015 1 commit
  24. 21 Jan, 2014 1 commit
  25. 20 Jan, 2014 1 commit
  26. 19 Jan, 2014 3 commits
  27. 18 Jan, 2014 1 commit
  28. 17 Jan, 2014 1 commit
    • Tim M's avatar
      Both STREAM and ROUTER sockets suffer from a naming problem on outbound… · 5d4860ea
      Tim M authored
      Both STREAM and ROUTER sockets suffer from a naming problem on outbound connections. While these connections can be created, they can't be immediately used. Traffic must be received before it can be sent. This prevents practical, minimal usage of STREAM or ROUTER as a true N fan in/out socket.
      
      This change simply provides the user with a socket option that sets a user defined name of the next outbound connection:
      
      zmq_setsockopt(routerSock,ZMQ_NEXT_IDENTITY,"myname",6);
      if(0 > zmq_connect(routerSock,"tcp://127.0.0.1:1234")) return 1;
      ret = zmq_send(routerSock,"myname",6,ZMQ_SNDMORE);
      zmq_send(routerSock,b.mem,b.used,0);
      
      In this example, the socket is immediately given the name "myname", and is capable of immediately sending traffic.
      
      This approach is more effective in three ways:
      1) It prevents all sorts of malicious peer naming attacks that can cause undefined behavior in existing ROUTER connections. (Two connections are made that both transmit the same name to the ROUTER, the ROUTER behavior is undefined)
      2) It allows immediate control of connections made to external parties for STREAM sockets. Something that is not possible right now. Before an outbound connection had no name for STREAM or ROUTER sockets because outbound connections cannot be sent to without first receiving traffic.
      3) It is simpler and more general than expecting two ROUTER sockets to handshake on assigned connection names. Plus it allows inline sending to new connections on ROUTER.
      5d4860ea
  29. 02 Jan, 2014 1 commit
  30. 28 Oct, 2013 1 commit
  31. 31 Aug, 2013 1 commit
    • Shawn J. Goff's avatar
      Change name of icanhasall to subscribe_to_all · 6a18f595
      Shawn J. Goff authored
      icanhasall is cute (for now), but the effect of the variable is clear
      only after tracking down its origin reading the commit. This change is
      intended to make it easier for people to have some intuition about its
      effect from its name.
      6a18f595
  32. 29 Jun, 2013 2 commits
  33. 28 Jun, 2013 2 commits