Re: [zeromq-dev] [REP-REQ] Sockets timeouts and connection reset

; PeerA >- [RST,ACK], PeerA -> PeerB >- [TCP Retransmission], PeerB -> PeerA >- [RST,ACK], PeerA -> PeerB > > > > Victor > > > > *De : *Francesco <francesco.monto...@gmail.com> > *Envoyé le :*Saturday, April 7, 2018 11:06 AM > *À : *

Re: [zeromq-dev] [REP-REQ] Sockets timeouts and connection reset

Retransmission], PeerB -> PeerA * [RST,ACK], PeerA -> PeerB Victor De : Francesco<mailto:francesco.monto...@gmail.com> Envoyé le :Saturday, April 7, 2018 11:06 AM À : ZeroMQ development list<mailto:zeromq-dev@lists.zeromq.org> Objet :Re: [zeromq-dev] [REP-REQ] Sockets timeout

Re: [zeromq-dev] [REP-REQ] Sockets timeouts and connection reset

Hi Victor, 2018-04-06 17:44 GMT+02:00 DUMAS, Victor : > In order to not block forever each socket has sending and receiving > timeouts. In case those timeouts are reached the sockets are destroyed and > recreated. > this statement has triggered my attention: why would

[zeromq-dev] [REP-REQ] Sockets timeouts and connection reset

Hello, Context: I have 2 peers, let’s call them: - PeerA under Linux using cppzmq version 4.1.3 - PeerB under Windows using NetMQ version 4.0.0 I need a mailbox between the 2 of them with 3 reliability guarantees: * Every message is delivered once and only once * Every message sent