[RFC] caching mechanism for rarely changed data (profile info / user absence)
Open
Nobody has claimed this yet.
feature: frontend 🖌️
performance 🚀
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 586
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
Need to implement some sort of caching mechanism for profile information (and user absence, e.g.). Set TTL to 6/12/24 hours.
Originally posted by @Antreesy in https://github.com/nextcloud/spreed/pull/14926#discussion_r2081242066
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name any files, tests, or entry points. Start by locating where profile information and user absence are fetched, then determine where a cache and TTL would fit. Done means an agreed caching mechanism covers both cases with a defined TTL and clear invalidation behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100