Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cache found in back storage isn't set on front storage #83

Closed
kirmanie opened this issue May 9, 2017 · 3 comments
Closed

Cache found in back storage isn't set on front storage #83

kirmanie opened this issue May 9, 2017 · 3 comments

Comments

@kirmanie
Copy link
Contributor

kirmanie commented May 9, 2017

After a memory warning causes the clearing of the front storage (memory), all future cache requests will resolve from the back storage (disk), never the front storage.

This is because, after resolving from back storage, we don't set front storage with the results of back storage. Is this by design?

@vadymmarkov
Copy link
Contributor

It's by initial design, yes. But it can be improved.

@kirmanie
Copy link
Contributor Author

@vadymmarkov thanks! Don't know much about the vision and direction of the project but took a crack at this issue anyway in this PR. Would be interested in hearing your thoughts.

@kirmanie
Copy link
Contributor Author

Closing this issue because it was resolved in this PR which got merged in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants