Closed
Description
I've been sitting on this for a while as a future feature but hadn't documented it.
The API would allow specifying a cache interaction policy both "downward" on the load and "upward" back through the processing. Through this you can facilitate complex cache interactions for both valid and seemingly-questionable use cases.
Random subset of interactions from other issues:
- Skip memory cache "downward" only.
- Skip memory cache "upward" only.
- Load from local cache (memory or disk) only.
- Force re-load from network.
I'm not going to do a full-on API strawman, but I know we'll probably want some EnumSet
action with
public enum BitmapSource { MEMORY, DISK, NETWORK }
public enum BitmapSink { MEMORY, DISK }
This API will trump the existing weak skipCache()
method on RequestCreator
.
Metadata
Metadata
Assignees
Labels
No labels