Cache first policy #1175
peterplamenovpenchev
started this conversation in
Ideas
Replies: 1 comment 3 replies
-
Unfortunately I don't think this is possible to implement since Coil's image pipeline is built around returning one drawable per request. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I am using the
1.4.0
version of the library & it's been a blast.There is one thing that appears to be missing though: cache first policy when loading images.
Here is the setup that I am working with:
Last-Modified
headerLast-Modified
header is used in subsequent requests asIf-Modified-Since
304
-> Not modified200 + body
-> if the image was modified since the last requestThis as you know is pretty standard setup so nothing interesting by far.
Now what I think would be cool is to have a cache first policy. I am thinking of the following behaviour:
Sadly I haven't got the chance to play around with the
2.0.0
version - does it support that kind of behaviour?And if not - is there a chance we would see something like that in the future?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions