1. 05 Apr, 2019 1 commit
  2. 02 Feb, 2019 1 commit
  3. 02 Feb, 2018 1 commit
  4. 10 Dec, 2016 1 commit
  5. 03 Feb, 2016 1 commit
    • Ilya Kulakov's avatar
      Make VMCI to work on Windows. · 538e5d47
      Ilya Kulakov authored
      select was improved to support multiple service providers on Windows.
      it should be slightly faster because of optimized iteration
      over selected sockets.
      538e5d47
  6. 28 Jan, 2016 1 commit
  7. 22 Jan, 2016 1 commit
  8. 08 Dec, 2015 1 commit
    • Ilya Kulakov's avatar
      Add the VMCI transport. · 68b13fbd
      Ilya Kulakov authored
      VMCI transport allows fast communication between the Host
      and a virtual machine, between virtual machines on the same host,
      and within a virtual machine (like IPC).
      
      It requires VMware to be installed on the host and Guest Additions
      to be installed on a guest.
      68b13fbd
  9. 06 Sep, 2015 1 commit
  10. 02 Jun, 2015 1 commit
  11. 22 Jan, 2015 1 commit
  12. 02 Jan, 2014 2 commits
  13. 01 Nov, 2013 2 commits
    • Erik Hugne's avatar
      zmq: narrow condition to include TIPC in build/test · 58ac87de
      Erik Hugne authored
      As TIPC transport for 0MQ will only work on post 3.8
      Linux kernels where nonblocking connect was added,
      we add AC_RUN test to check for this functionality.
      Should the test fail, tipc is excluded from build/test.
      Signed-off-by: 's avatarErik Hugne <erik.hugne@ericsson.com>
      58ac87de
    • Erik Hugne's avatar
      zmq: add support for TIPC transport · eab85b52
      Erik Hugne authored
      A ZeroMQ application can opt for TIPC based sockets
      using the TIPC port name format:
      zmq_bind(sb, "tipc://{type,lower,upper}");
      zmq_connect(sc, "tipc://{type,inst}");
      
      'type' is the service ID, and 'lower/upper' can be
      used for service partitioning or basic load
      balancing.
      
      ZeroMQ TIPC transport requires a kernel >= 3.8
      (nonblocking connect support for TIPC).
      Signed-off-by: 's avatarErik Hugne <erik.hugne@ericsson.com>
      eab85b52
  14. 15 Jun, 2013 1 commit
  15. 17 May, 2013 1 commit
    • Pieter Hintjens's avatar
      plain_mechanism now uses options.as_server · f909b9c7
      Pieter Hintjens authored
      - we need to switch to PLAIN according to options.mechanism
      - we need to catch case when both peers are as-server (or neither is)
      - and to use username/password from options, for client
      f909b9c7
  16. 14 May, 2013 1 commit
    • Martin Hurton's avatar
      Implement ZMTP/3.0 PLAIN mechanism · 4eecda8a
      Martin Hurton authored
      This implements protocol handshake.
      We still need to design and implement 1) API changes so a user
      can set username and password, and 2) a mechanism for engine
      to authenticate users.
      4eecda8a
  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. 22 Jan, 2013 1 commit
  19. 21 Jan, 2013 1 commit
  20. 17 Nov, 2012 1 commit
  21. 30 Sep, 2012 1 commit
  22. 21 Sep, 2012 1 commit
  23. 04 Aug, 2012 1 commit
  24. 13 Jul, 2012 1 commit
  25. 11 Jul, 2012 1 commit
  26. 13 Jun, 2012 1 commit
  27. 12 Jun, 2012 2 commits
  28. 11 Jun, 2012 1 commit
  29. 05 Jun, 2012 1 commit
  30. 04 May, 2012 1 commit
  31. 21 Apr, 2012 1 commit
    • Sergey KHripchenko's avatar
      fixes for zmq_unbind() / zmq_disconnect() usage corner cases · 057fab09
      Sergey KHripchenko authored
      1. when we call zmq_bind()/zmq_connect() to create endpoint
      we send ourselfs(through launch_child()) command to process_own(endpoint)
      (and add it to own_t::owned)
      in the application thread we could call zmq_unbind() / zmq_disconnect() _BEFORE_
      we run process_own() in ZMQ thread and in this situation we will be unable to find it in
      own_t::owned. in other words own_t::owned.find(endpoint) will not be deleted but it will be deleted from
      socket_base_t::endpoints.
      
      2. when you zmq_unbind() the lisnening TCP/IPC socket was terminated only in destructor...
      so the whole ZMQ_LINGER time listening TCP/IPC socket was able to accept() new connections
      but unable to handle them.
      
      this all geting even worse since unfortunately zmq has a bug and '*_listener_t' object not terminated
      untill the socket's zmq_close().
      AT LEAST FOR PUSH SOCKETS.
      Everything is ok for SUB sockets.
      
      Easy to reproduce without my fix:
      
      zmq_socket(PUSH)
      zmq_bind(tcp);
      // connect to  it from PULL socket
      zmq_unbind(tcp);
      
      sleep(forever)
      
      // netstat -anp | grep 'tcp listening socket'
      
      With my fix you could see that after zmq_unbind(tcp) all previously connected tcp sessions
      will not be finished untill the zmq_close(socket) regardless of ZMQ_LINGER value.
      
      (*_listener_t terminates all owned session_base_t(connect=false) and they call pipe_t::terminate()
      which in turn should call session_base_t::terminated() but this never happens)
      057fab09
  32. 18 Apr, 2012 1 commit
  33. 01 Mar, 2012 1 commit
  34. 18 Feb, 2012 1 commit
  35. 17 Feb, 2012 1 commit
  36. 16 Feb, 2012 1 commit
  37. 14 Feb, 2012 1 commit