![]() Otherwise, if I have to deal with the fact that the cache cleanup process may happen anytime, anywhere, even during app execution, use of in memory data structures would be useless because they would eventually become out of sync with the real contents of the folder in the event of the OS deciding to clean up files by itself. ![]() For example, I could use a map (in memory) of cached entries (files stored on the cache folder) containing time stamps of cache hits and other information that might be useful to prioritize the way cached entries are recycled. If I could assume the OS won't mess with the cached files during execution, I would be able to use "in memory" data structures to optimize my cache implementation. While I know the Android OS may decide to clear files from the cache directory of my application to free up internal storage space, I'm not quite sure if this "cleanup" process can happen even during its execution. I am implementing an image file cache in my application to reduce the number of times these files are downloaded directly from the web server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |