In message <19990601192912.68cc115...@hub.freebsd.org>, "Jonathan M. Bresler" w
rites:
> we should consult with hte tcp-impl mailing list and get their
>take on the matter before we decide what to do here. the address is
>tcp-i...@grc.nasa.gov.
I already did, but it is such a hot issue that they don't get into it.
A good summary of the "traditionalist" view can be found in:
http://tcp-impl.grc.nasa.gov/tcp-impl/list/archive/1246.html
I agree in principle, but not in practice.
Having no keep-alives just doesn't work when WIN* boxes drop carrier
and get another IP# when they come back, or when they just randomly
crashes...
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.
Of course if the application has particular hysteric requirements
(ircd anyone) it can implement its own methods as well.
--
Poul-Henning Kamp FreeBSD coreteam member
p...@freebsd.org "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
