search

JackYeh / s3fs

Automatically exported from code.google.com/p/s3fs
GNU General Public License v2.0
0 stars 0 forks source link

local file cache: just use mtime and size (instead of md5) kinda like rsync does?!? #23

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
local file cache: just use mtime and size (instead of md5) kinda like rsync
does?!?

Original issue reported on code.google.com by rri...@gmail.com on 2 Apr 2008 at 12:39

GoogleCodeExporter commented 8 years ago 
the reasoning behind this is to lower cpu usage, however, should really be
calculating and comparing Content-MD5 anyway to verify end to end integrity

Original comment by rri...@gmail.com on 11 Aug 2008 at 5:21

GoogleCodeExporter commented 8 years ago 
Ben,  can you comment on this one as you have been working on the cache 
function. Thanks. Dan

Original comment by dmoore4...@gmail.com on 9 Mar 2011 at 5:13

GoogleCodeExporter commented 8 years ago 
I like the idea of this because it potentially fixes issue 160 and removes a 
few crypto requirements. I'll see what I can come up with.

Original comment by ben.lema...@gmail.com on 9 Mar 2011 at 5:40

GoogleCodeExporter commented 8 years ago 
see r338

I'm happy with the results of this change which did end up fixing #160 as well. 
The change requires the locally cached file mtime to be hacked in order to 
match that of the file we uploaded/downloaded from s3.

Original comment by ben.lema...@gmail.com on 10 Mar 2011 at 12:19