1. 17 Apr, 2020 3 commits
    • Doron Somech's avatar
      problem: router doesn't know when peer disconnected · 81444136
      Doron Somech authored
      ZMQ_ROUTER_NOTIFY doesn't have a context and doesn't play nice with protocols. with ZMQ_DISCONNECT_MSG we can set it to a protocol message, like DISCONNECT in majordomo. Router will send it when a peer is disconnected. Another advantage of ZMQ_DISCONNECT_MSG is that it also works on inproc.
      
      Together with ZMQ_HEARTBEAT it allows to build very reliable protocols, and much simpler as well.
      81444136
    • Luca Boccassi's avatar
      Merge pull request #3870 from somdoron/HELLO_MSG · 4c1d720a
      Luca Boccassi authored
      problem: ZMQ_HEARTBEAT is not useful without sending an hello message
      4c1d720a
    • Doron Somech's avatar
      problem: ZMQ_HEARTBEAT is not useful without sending an hello message · 93da6763
      Doron Somech authored
      When using ZMQ_HEARTBEAT one still needs to implement application-level heartbeat in order to know when to send a hello message.
      For example, with the majordomo protocol, the worker needs to send a READY message when connecting to a broker. If the connection to the broker drops, and the heartbeat recognizes it the worker won't know about it and won't send the READY msg.
      To solve that, the majordomo worker still has to implement heartbeat. With this new option, whenever the connection drops and reconnects the hello message will be sent, greatly simplify the majordomo protocol, as now READY and HEARTBEAT can be handled by zeromq.
      93da6763
  2. 13 Apr, 2020 5 commits
  3. 09 Apr, 2020 5 commits
  4. 23 Mar, 2020 2 commits
  5. 18 Mar, 2020 2 commits
  6. 17 Mar, 2020 3 commits
  7. 14 Mar, 2020 6 commits
  8. 07 Mar, 2020 5 commits
  9. 29 Feb, 2020 2 commits
  10. 28 Feb, 2020 1 commit
  11. 24 Feb, 2020 4 commits
  12. 23 Feb, 2020 2 commits