TCP's timeouts are perfectly fine, and the only thing you might be showing above is that the application timeouts are too short or that TCP needs notifications.
The application timeouts are probably being driven by external desires for a given recovery time.
TCP notifications don't solve anything unless the links in question are local to the machine on which the TCP endpoint resides.
So, it seems that what this is really saying is that in the context of Linux at least, TCP is not a suitable protocol to be used in situations where a fast detection/recovery is desired.
Does that pretty much sum it up? rick jones - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
