Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!VENERA.ISI.EDU!braden
From: braden@VENERA.ISI.EDU
Newsgroups: comp.protocols.tcp-ip
Subject: Re: partial transfer recovery in RFC and OSI protocols
Message-ID: <9001022258.AA12888@braden.isi.edu>
Date: 2 Jan 90 22:58:13 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 12


	I suppose that the way this would be dealt with is for the receiver to
	store an auxiliary file, with indications of "when I began record m,
	n bytes had been sent".  This file would be periodically updated (every
	few hundred records) and pushed to the disk.  Some care would need to be
	taken to ensure that the received file and the marker file would be
	consistent after a crash.

The restart mechanism built into FTP is essentially a nice version of what
you suggest.

Bob Braden