Hi,

Thank for your advise. However, after I tranfer my file,
my application had to test that the file is successfully transfer to
server side, then had to delete it on my local location. The server
will not check it integrity.

For transfer protocols, I think they work because both side of the
transfer are same protocol which are monitoring the transfer, hence
they can resend if any integrity of the file is detected.



>Can you include a CRC as part of the file transfer? Create CRC on the client side. Send it along with the file to the server. Have the server perform the same CRC check and compare it to the CRC sent. If it doesn't match then request the file again; if it does match, you're okay.
>
>I believe some of the transfer protocols (XModem, YModem) use this method, although I can't be sure.
>
>HTH.
>
>>Hi,
>>
>>I am creating an client application that will auto dial in to my server
>>and do some file transfer of any stuff of file.
>>
>>My client is running on Win2k whileas my server might be running OS like
>>Linux, HP UX.
>>
>>So, in order to ensure that any file transfer is successfully, I do some
>>checking like ensure that the zip file transfer/any file transfer exist
>>first and that both source and destination file size are the same.
>>
>>But, it seem like different OS reported different filesize, so how
>>can I solve this issue to ensure that my file transfer is okay.
>>I can't use CRC check as not all my files are zip files, even if they
>>are zip files, CRC check on server side from client side is very slow and
>>unreliable too.
>>
>>So, anyone had any good ideal to overcome this issue.
>>Please kindly help and comment on this issue. Thank you.