FlashFXP Forums - View Single Post - "Only resume files transferred in binary mode"

MxxCon · 03-31-2005, 01:19 AM

as you may know the reason for ASCII transfer mode..
different OS handle txt files slightly differently. some use LF to indicate line end, some use CR/LF(some use something else?)
when you transfer file in ASCII mode, you tell server to handle it the way it thinks is best..
if you will transfer same file in BIN mode, you'll transfer it 100% as it is. side effect of that is that often your favorite warez nfos or sfv will have extra lines.

so, when you transfer a file in ASCII mode you let server add/remove LF/CR characters. results of that is sometimes txt file will have different size on the server than locally, even tho it is really complete.
so obviously resuming such file would be bad.
and most of the time txt files are small so difference between resuming them and uploading whole new file is 0.

03-31-2005, 01:19 AM
MxxCon Super Duper Join Date: Oct 2001 Location: Brooklyn, NY Posts: 3,881	as you may know the reason for ASCII transfer mode.. different OS handle txt files slightly differently. some use LF to indicate line end, some use CR/LF(some use something else?) when you transfer file in ASCII mode, you tell server to handle it the way it thinks is best.. if you will transfer same file in BIN mode, you'll transfer it 100% as it is. side effect of that is that often your favorite warez nfos or sfv will have extra lines. so, when you transfer a file in ASCII mode you let server add/remove LF/CR characters. results of that is sometimes txt file will have different size on the server than locally, even tho it is really complete. so obviously resuming such file would be bad. and most of the time txt files are small so difference between resuming them and uploading whole new file is 0. __________________ [Sig removed by Administrator: Signature can not exceed 20GB]