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
Although it's unfortunate, content at uris can change without the uri changing so we can't reliably invalidate cache files. We can get around this for media store uris only by requiring users to pass in additional data from the media store (see http://bumptech.github.io/glide/javadocs/latest/com/bumptech/glide/RequestManager.html#loadFromMediaStore(android.net.Uri, java.lang.String, long, int)). This data must be available at the time the request is made so that we can construct the key for the memory cache synchronously.
To fix this, we should:
Default to DiskCacheStrategy.NONE for Uris (other than http/https).
Default to not caching loads for Uris in the memory cache.
Provide a nicer api for loading a Uri with some kind of cache buster string that can be mixed into the cache key for those who want to take on the responsibility of handling cache invalidation themselves.
See #172 for an example of where our current behavior can cause problems.
The text was updated successfully, but these errors were encountered:
Although it's unfortunate, content at uris can change without the uri changing so we can't reliably invalidate cache files. We can get around this for media store uris only by requiring users to pass in additional data from the media store (see http://bumptech.github.io/glide/javadocs/latest/com/bumptech/glide/RequestManager.html#loadFromMediaStore(android.net.Uri, java.lang.String, long, int)). This data must be available at the time the request is made so that we can construct the key for the memory cache synchronously.
To fix this, we should:
See #172 for an example of where our current behavior can cause problems.
The text was updated successfully, but these errors were encountered: