[zeromq-dev] Forwarder stops forwarding

Robin Weisberg robin at scout-trading.com
Wed Jun 16 15:16:27 CEST 2010

Well you can just set the limit appropriately if you plan on sending 10GB messages. Also on the receiving end as long as you are receiving data for a message you know the connection is still alive so even if it takes 2 minutes to read a huge message, it shouldn't time out since you are still receiving data. You would only disconnect if you didn't receive any data at all for X millis. 

-----Original Message-----
From: zeromq-dev-bounces at lists.zeromq.org [mailto:zeromq-dev-bounces at lists.zeromq.org] On Behalf Of Martin Sustrik
Sent: Wednesday, June 16, 2010 9:09 AM
To: 0MQ development list
Subject: Re: [zeromq-dev] Forwarder stops forwarding

Robin Weisberg wrote:

> My vote would be to just keep it simple. Debugging and reading a
> tcpdump will be more confusing if you have to figure out why a
> heartbeat was/wasn't sent based on fancy heuristics.


> I like the idea of sending if there hasn't been any other message
> sent in the past X milliseconds and make X a socket option.

That can backfire in case of large messages. If timeout is 1 sec and 
transfer of 10GB messages takes 10 secs. The connection would timeout 
during the message transmission.

zeromq-dev mailing list
zeromq-dev at lists.zeromq.org

More information about the zeromq-dev mailing list