• Subject: RE: Error Recovery in FTP
  • From: "Murphy, Guy" <murphy@xxxxxxxxxxxxxxxxx>
  • Date: Thu, 18 Mar 1999 09:19:03 -0600

        I believe that error detection and recovery is handled in the tcp
part of tcp/ip.


Guy Murphy    
University of Illinois
FACTS system
217-333-8670
murphyfa@uiuc.edu


-----Original Message-----
From: Liu Kean Keong (HLB) [mailto:LiuKeanKeong@hlbb.hongleong.com.my]
Sent: Wednesday, March 17, 1999 9:42 PM
To: 'MIDRANGE-L@midrange.com'
Subject: Error Recovery in FTP


I read from the FTP Specification RFC 959 that there is 'no provision
for detecting bits lost or scrambled in data transfer'. A restart
procedure is provided to retransmit but controlled at user application
level. (compared to SNA which handles it for us at a lower level?)

Does this mean that there is a remote chance that a FTPed file may have
bits that are in error? In which case we would need to program in a
checksum feature into our FTP file transfer programs? I mean, for
critical data files.  not for bitmap, jpg or wav files which are
tolerent of bit errors!  :-)

any comments welcomed. thanks.

kk liu.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].