Lost cache in some condition about disklrucache HOT 7 OPEN

This is a policy decision in the API. You can manually call flush() in your own code if you'd like to flush the journal after every write. DiskLruCache doesn't do this by default because it wants to minimize the number of slow disk writes it makes.

from disklrucache.

That said, this does need to be documented!

from disklrucache.

I see your point. I'd like not flush journal after every write, only after write "CLEAN" or "DIRTY", while not flush after write "READ"(not worth to do).
Back to my case, my app is an android app which may be closed or interrupted unpredictably, and I has only one chance to create a cache(after a video is downloaded) and use it elsewhere. If someone has the similar case with me, I suggest flush after every commit immediately.

from disklrucache.

@swankjesse could you suggest where it is better to flush DiskLruCache for Android apps to prevent loosing of image cache after app close or crash?

from disklrucache.

Calling flush after committing an edit would work.

from disklrucache.

Thanks!

from disklrucache.

Thank you so much for this, flush works!

from disklrucache.