> Saying that it should be an application function is bogus in my
> book, since the problem is valid for all TCP users, and there are
> clearly not any reason to duplicate the code in telnetd, ftpd,
> talkd, &c &c.
But the problem is that every application uses TCP a little bit
differently, and so the type of timeout logic that is appropriate for one
application is not the same as the timeout that's appropriate for another.
What type of timeout you want in a TCP connection really depends upon what
you are going to do with it, and that the kernel cannot know.
If an application does not timeout a TCP connection in a sane way, it is
broken. It should be fixed. 'Fixing' it in the kernel simply allows the
application to remain broken.
DS
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
