1. 31 Aug, 2018 2 commits
  2. 09 Aug, 2018 1 commit
  3. 31 May, 2018 1 commit
  4. 28 May, 2018 1 commit
  5. 27 May, 2018 2 commits
  6. 26 May, 2018 1 commit
  7. 22 May, 2018 2 commits
  8. 18 May, 2018 1 commit
  9. 16 May, 2018 1 commit
  10. 15 May, 2018 1 commit
  11. 14 May, 2018 1 commit
  12. 13 May, 2018 1 commit
  13. 10 May, 2018 1 commit
  14. 09 May, 2018 1 commit
  15. 20 Mar, 2018 1 commit
  16. 19 Mar, 2018 1 commit
  17. 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
  18. 02 Feb, 2018 1 commit
  19. 08 Aug, 2017 1 commit
    • Simon Giesecke's avatar
      Problem: ZAP status codes != 200 do not result in an appropriate monitor event (#2665) · a6cef4ef
      Simon Giesecke authored
      * Problem: missing test for status code 300, inadequate assertion for status code 500
      
      Solution: add test, change assertion (currently test fails)
      
      * Problem: gcc compiler error deprecated conversion from string constant
      
      Solution: declare variable as const
      
      * Problem: in case of ZAP handler returning a status code other than 200, no appropriate event is emitted
      
      Solution: immediately emit event after receiving reply from ZAP handler
      
      * Problem: endpoint address is not included in zap-reply monitor event
      
      Solution: added functions to retrieve endpoint address in zmq::i_engine and zmq::session_base_t
      removed unused code block in zmq::stream_engine_t::next_handshake_command
      
      * Problem: wrong formatting
      
      Solution: fix formatting
      
      * Problem: test fails because of EPIPE
      
      Solution: add EPIPE/ECONNRESET/ECONNAGAIN handling for more test cases
      a6cef4ef
  20. 31 Jul, 2017 2 commits
    • Luca Boccassi's avatar
      Problem: ZMQ_BINDTODEVICE not used for ZMQ_DISH · bb0b518e
      Luca Boccassi authored
      Solution: apply the option outside of the send/recv_enabled blocks so
      that it is used for all types of UDP sockets
      bb0b518e
    • Brian Russell's avatar
      Add socket option BINDTODEVICE · b963542e
      Brian Russell authored
      Linux now supports Virtual Routing and Forwarding (VRF) as per:
      
      https://www.kernel.org/doc/Documentation/networking/vrf.txt
      
      In order for an application to bind or connect to a socket with an
      address in a VRF, they need to first bind the socket to the VRF device:
      
          setsockopt(sd, SOL_SOCKET, SO_BINDTODEVICE, dev, strlen(dev)+1);
      
      Note "dev" is the VRF device, eg. VRF "blue", rather than an interface
      enslaved to the VRF.
      
      Add a new socket option, ZMQ_BINDTODEVICE, to bind a socket to a device.
      In general, if a socket is bound to a device, eg. an interface, only
      packets received from that particular device are processed by the socket.
      
      If device is a VRF device, then subsequent binds/connects to that socket
      use addresses in the VRF routing table.
      b963542e
  21. 01 Jun, 2016 1 commit
  22. 18 May, 2016 1 commit
  23. 16 May, 2016 3 commits
  24. 15 May, 2016 1 commit
  25. 14 May, 2016 1 commit
  26. 21 Feb, 2016 5 commits
  27. 18 Feb, 2016 1 commit
  28. 07 Feb, 2016 1 commit
  29. 01 Feb, 2016 1 commit
  30. 30 Jan, 2016 1 commit