Path: utzoo!mnetor!uunet!husc6!bloom-beacon!mit-eddie!rutgers!aramis.rutgers.edu!athos.rutgers.edu!hedrick From: hedrick@athos.rutgers.edu (Charles Hedrick) Newsgroups: comp.protocols.tcp-ip Subject: Re: Another problem with usage charges Message-ID: Date: 30 Apr 88 01:32:59 GMT References: <8804260944.AA25473@ucbvax.Berkeley.EDU> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 10 To: VALDIS@CLVM.CLARKSON.EDU In many cases there are things the local site can do to improve the reliability of long-distance FTP's. The problem of getting 95% of a file and then having the connection break is often due to a bug in your TCP that causes it to interrupt the connection when it gets a transient error message. Newer versions of TCP and gateway code can also make a dramatic difference. I'm not sure that I approve of usage-sensitive charging, at least in the research context. But if we're going to do it, paying for broken connections may not be so bad. At the moment, people don't have much incentive to clean up old, decrepit TCP's.