On Fri, Jan 05, 2007 at 09:49:44AM +0530, kuriakose wrote:
> Thanks for the reply.
> So we need to store the last modified server time along with the partially
> downloaded file. But this has to be in a sepearate file along with the main
> file . Hope what I got is correct.
> Thanks once again.

Storing last modified server time might be sufficient depending on
your application, but if the file changes within one second of the previous
modification the modification time won't change but the file contents will.
Where you store that metadata doesn't matter--in a separate file or in the
filesystem's metadata store for the downloaded file (i.e. the file's
modification date). Are you expecting any part of the file to change,
or just new data to be appended? How critical is it that you don't miss any
changes? Do you have a way to verify that the final downloaded file is
correct (e.g. CRC, MD5, cryptographic signature)? Answering those questions
will give you a better idea of whether using modification time and content
length is good enough. Using the ETag gives you a much more reliable
way to tell if the remote file has changed.

>>> Dan

-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved