Date: Tue, 1 Jun 1999 13:20:16 -0700 From: "David Schwartz" <davids@webmaster.com> To: "Poul-Henning Kamp" <phk@critter.freebsd.dk>, "Jonathan M. Bresler" <jmb@hub.freebsd.org> Cc: <current@FreeBSD.ORG> Subject: RE: net.inet.tcp.always_keepalive on as default ? Message-ID: <000101beac6c$29979d00$021d85d1@whenever.youwant.to> In-Reply-To: <22444.928268157@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000101beac6c$29979d00$021d85d1>