Skip to content

Caching strategy #230

@tfius

Description

@tfius

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

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions