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

[ENHANCEMENT]: web-ui: Rework frontend Cache #1211

Open
gluafamichl opened this issue Mar 26, 2025 · 0 comments
Open

[ENHANCEMENT]: web-ui: Rework frontend Cache #1211

gluafamichl opened this issue Mar 26, 2025 · 0 comments
Assignees
Labels
enhancement Enhancement of existing features / Small addition ui Hashtopolis UI related

Comments

@gluafamichl
Copy link
Contributor

gluafamichl commented Mar 26, 2025

Description

There are several problems concerning the frontend cache:

  • Cache has no delete or invalidate method, maybe we should delete cached objects after they have no hit after a defined time period, think about using LRU and/or TTL
  • Editable objects must not use database ID as cache key, changes to an attribute will not be updated in Cache
  • Cache key calculation from input properties is invalid, if a property point to a nested array, cache keys may point to invalid entries
  • Cache is currently not thread-safe, may lead to race conditions?
@gluafamichl gluafamichl added enhancement Enhancement of existing features / Small addition ui Hashtopolis UI related needs investigation Devs still need to investigate labels Mar 26, 2025
@gluafamichl gluafamichl self-assigned this Mar 28, 2025
@gluafamichl gluafamichl removed the needs investigation Devs still need to investigate label Mar 28, 2025
@ObsidianOracle ObsidianOracle moved this to 🚧 In progress in 🐰 Sprint April '25 Mar 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement of existing features / Small addition ui Hashtopolis UI related
Projects
Status: No status
Status: 🚧 In progress
Status: No status
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant