You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Say I have dozens of images in disk cache. And my app uses some of them frequently, and doesn't want those to expire. How would I prevent Kingfisher from expiring them? More specifically, say:
1 I have 50 images cached in disk, and my app accesses 30 of them. By "accesses", I mean calling kf_setImageWithURL to supply the image;
2 I set up maxCachePeriodInSecond to be 7 days, with the intention that images not accessed in the last 7 days will be expired, and purged.
So in such a setting, would calling kf_setImageWithURL extend the image's expiration date to 7 days from the moment of calling? If not, what can I do to extend it?
Thanks!
The text was updated successfully, but these errors were encountered:
You stated:
"Maybe we should use the access day instead of modification date to check the expiration. It might work better."
In all fairness, I agree with you on using something other than modification date to check for expiration. Using modification date doesn't seem all that elegant to me. After all, if the app keeps reading the image without modifying it, the image should be kept in cache for faster processing, right?
Say I have dozens of images in disk cache. And my app uses some of them frequently, and doesn't want those to expire. How would I prevent Kingfisher from expiring them? More specifically, say:
1 I have 50 images cached in disk, and my app accesses 30 of them. By "accesses", I mean calling kf_setImageWithURL to supply the image;
2 I set up maxCachePeriodInSecond to be 7 days, with the intention that images not accessed in the last 7 days will be expired, and purged.
So in such a setting, would calling kf_setImageWithURL extend the image's expiration date to 7 days from the moment of calling? If not, what can I do to extend it?
Thanks!
The text was updated successfully, but these errors were encountered: