On 14-sep-2007, at 22:34, Greg Skinner wrote:
When routing connectivity could be restored quickly, the maintained
state
at both ends of the TCP connection would allow the application to
proceed normally. However, this practice doesn't seem to have made it
into the application-writing community at large, because lots of
applications fail for just this reason.
What I experienced is that when logged in to a Unix machine from a
Windows machine, if the address went away or the connectivity was
lost and an ICMP unreachable came back, the Windows box would
terminate the session, while pretty much everything else would keep
the session alive for some time so you could put the address back /
restore connectivity and the session was still there if the other
side hand't timed out / reset.
_______________________________________________
Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf