1. 27 May, 2018 1 commit
  2. 22 May, 2018 1 commit
  3. 02 Feb, 2018 1 commit
  4. 28 Jan, 2016 1 commit
  5. 02 Jun, 2015 1 commit
  6. 26 Jan, 2015 1 commit
    • Julien Ruffin's avatar
      Added socket option ZMQ_INVERT_MATCHING. · cf2238f8
      Julien Ruffin authored
      ZMQ_INVERT_MATCHING reverses the PUB/SUB prefix matching. The subscription
      list becomes a rejection list. The PUB socket sends messages to all
      connected (X)SUB sockets that do not have any matching subscription.
      
      Whenever the option is used on a PUB/XPUB socket, any connecting SUB
      sockets must also set it or they will reject everything the publisher
      sends them. XSUB sockets are unaffected because they do not filter out
      incoming messages.
      cf2238f8
  7. 22 Jan, 2015 1 commit
  8. 08 Aug, 2014 1 commit
  9. 02 Jan, 2014 1 commit
  10. 06 Jun, 2013 1 commit
  11. 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
  12. 09 Nov, 2012 1 commit
  13. 09 Nov, 2011 1 commit
  14. 01 Nov, 2011 1 commit
  15. 31 Oct, 2011 1 commit
  16. 12 Jun, 2011 1 commit
  17. 11 Jun, 2011 1 commit
  18. 23 May, 2011 1 commit
  19. 22 May, 2011 1 commit
    • Martin Sustrik's avatar
      Introduces bi-directional pipes · acf0b0e5
      Martin Sustrik authored
      So far, there was a pair of unidirectional pipes between a socket
      and a session (or an inproc peer). This resulted in complex
      problems with half-closed states and tracking which inpipe
      corresponds to which outpipe.
      
      This patch doesn't add any functionality in itself, but is
      essential for further work on features like subscription
      forwarding.
      Signed-off-by: 's avatarMartin Sustrik <sustrik@250bpm.com>
      acf0b0e5
  20. 30 Apr, 2011 1 commit
  21. 21 Apr, 2011 1 commit
  22. 20 Mar, 2011 1 commit
  23. 02 Mar, 2011 1 commit
  24. 14 Jan, 2011 1 commit
  25. 13 Jan, 2011 1 commit
  26. 30 Oct, 2010 1 commit
  27. 18 Sep, 2010 1 commit
  28. 31 Aug, 2010 1 commit
  29. 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
  30. 27 Mar, 2010 2 commits
  31. 12 Mar, 2010 1 commit
    • Martin Hurton's avatar
      Implement flow control · 61ee6fae
      Martin Hurton authored
      This commit introduces the necessary changes necessary
      for implementing flow control. None of the socket types
      implements the flow control yet. The code will crash when
      the flow control is enabled and the thw lwm is reached.
      
      The following commits will add flow-control support for
      individual socket types.
      61ee6fae
  32. 05 Jan, 2010 1 commit
  33. 15 Dec, 2009 1 commit
  34. 24 Nov, 2009 1 commit
  35. 01 Oct, 2009 1 commit
  36. 23 Sep, 2009 1 commit
  37. 21 Sep, 2009 2 commits