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

Caching strategy #230

Open
tfius opened this issue Apr 19, 2023 · 0 comments
Open

Caching strategy #230

tfius opened this issue Apr 19, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@tfius
Copy link
Contributor

tfius commented Apr 19, 2023

Current caching lifecycle is not good and causes problems.

  • we don't know when connection was either interrupted or changed. (no event if you restart fdp-play or get offline)
  • we can't know when storage context was changed and data is no longer available. (Blossom can not store cache date)

Change implementation so caching is optional.
Introduce CacheProxy with following functionality:

  • explicit invalidation,
  • purge option and
  • refresh option
@tfius tfius added the enhancement New feature or request label Apr 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants