Add background uploading when using local cache

[GoogleCodeExporter]

When using a local cache, it would be nice if s3fs would return 
immediately after a file is closed, and allow more files to be created or 
written.

This would have the ramification of errors not being relayed to the 
client if an upload error occurred (such as connectivity lost) but s3fs 
could probably keep track of those things and retry upload when 
connectivity is resumed.

If this option was enabled, copious warnings should be given to the 
effect that just because the client returns, it does not mean the file is 
uploaded, don't turn off your machine, etc.

Original issue reported on code.google.com by pedah...@gmail.com on 10 Apr 2008 at 12:05

[GoogleCodeExporter]

This would be fantastic. An added bonus would be limiting the size of the cache 
somehow.

Thanks for all of your work on this project!

Original comment by br...@brianpuccio.net on 17 Apr 2009 at 8:03

[GoogleCodeExporter]

Original comment by ben.lema...@gmail.com on 23 Jun 2011 at 3:09

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Hi, all

This Issue has not been updated for a long time.
On using local cache, latest version v1.72 can use local cache files, and s3fs 
is changed many for cache logic.
Latest version does not support background uploading which this issue means, 
but s3fs writes bytes into local cache and return immediately. And when the 
file(object) is synced, s3fs only puts to S3.
It does not send redundant packets.

I closed this issue, but if you have more request about this logic(background 
uploading), please post new issue with this issue No.
(I'm sorry that I think I should arrange the issue of an old version.)

Please use and test latest version, and post new issue.

Thanks in advance.
Regards

Original comment by ggta...@gmail.com on 12 Aug 2013 at 4:33

• Changed state: Done