1. 06 Feb, 2019 3 commits
  2. 10 Aug, 2018 1 commit
  3. 30 May, 2018 1 commit
  4. 27 May, 2018 1 commit
  5. 10 Mar, 2018 1 commit
    • Manuel Segura's avatar
      Pull request to merge porting to WindRiver VxWorks 6.x (#2966) · 4726f726
      Manuel Segura authored
      * Problem: Still need to port over more files to VxWorks 6.x
      
      Solution: Port more files to VxWorks 6.x
      
      * Problem: Need to port over remaining files to VxWorks 6.x. Also remove POSIX thread dependency for VxWorks (because of priority inversion problem in POSIX mutexes with VxWorks 6.x processes)
      
      Solution: Port over remaining files to VxWorks 6.x. Also removed POSIX thread dependency for VxWorks
      
      * Problem: Needed to modify TCP, UDP, TIPC classes with #ifdefs to be compatible with VxWorks 6.x.
      
      Solution:  Modify TCP, UDP, TIPC classes with #ifdefs to be compatible with VxWorks 6.x
      4726f726
  6. 02 Feb, 2018 1 commit
  7. 18 Feb, 2016 1 commit
  8. 28 Jan, 2016 1 commit
  9. 02 Jun, 2015 1 commit
  10. 22 Jan, 2015 1 commit
  11. 01 Jul, 2014 1 commit
  12. 05 May, 2014 1 commit
    • Franco Fichtner's avatar
      ipc: fail harder for abstract ipc on non-Linux · fff29a4a
      Franco Fichtner authored
      Using 'ipc://@abstract-socket' on non-Linux platforms yields inconsistent
      behaviour.  Abstract sockets don't exist, so the literal file is created.
      The test previously failed, but for a different reason: this is not the
      directory you are looking for.  Now, zmq_bind() will fail for the right
      reason: the socket can't be created.  Put the XFAIL back.
      fff29a4a
  13. 02 Jan, 2014 1 commit
  14. 20 Dec, 2013 1 commit
  15. 07 Oct, 2013 1 commit
    • Brandon Carpenter's avatar
      Fix detection of abstract ipc pathname and length calculation. · e0f4d603
      Brandon Carpenter authored
      Abstract socket pathnames must have a NULL character in the first
      position, but the second character must also be checked to differentiate
      an abstract name from the empty string.  The address length must also
      indicate the length of the pathname because the kernel uses the entire
      address as the name, including NULL characters.  ZMQ uses
      NULL-terminated strings for the address, so the abstract address length
      is the length of the string following the initial NULL byte plus 3; two
      bytes for the address family and one for the initial NULL character.
      e0f4d603
  16. 04 Oct, 2013 1 commit
  17. 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
  18. 18 Apr, 2012 1 commit
  19. 16 Feb, 2012 1 commit
  20. 01 Nov, 2011 1 commit
  21. 31 Oct, 2011 1 commit
  22. 18 Aug, 2011 2 commits
  23. 15 Jul, 2011 1 commit
  24. 23 May, 2011 1 commit
  25. 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
  26. 21 Apr, 2011 1 commit
  27. 02 Mar, 2011 1 commit
  28. 05 Nov, 2010 1 commit
  29. 30 Oct, 2010 1 commit
  30. 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
  31. 28 Sep, 2010 1 commit
  32. 18 Sep, 2010 1 commit
  33. 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
  34. 04 Aug, 2010 1 commit
  35. 13 Mar, 2010 1 commit
  36. 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