On Fri, Oct 26, 2012 at 9:33 AM, Stephen Hemminger <[email protected]> wrote:
> The problem was related to setting identity on the DEALER. > Turns out than when the DEALER reconnects the internal ROUTER > code thinks the new socket is a duplicate of the old (still timing out) > socket and closes it. Ah, right. If the client didn't close the socket properly, TCP won't report the error for a while. Do you see anything we can do in the router socket to make this work better? Allowing duplicate identities won't work, and allowing a second client to "grab" the identity of an existing one won't work either. Perhaps we need ping-pong heartbeating in the socket layer. -Pieter _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
