Client-side filesystem cache
Open
Nobody has claimed this yet.
new feature
- Dominant language
- Java
- Stars
- 668
- Forks
- 135
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 7
Description
.. so that:
- client applications do not refuse to start due to the inability to retrieve the configuration
- clients send fewer number of requests potentially
Note that a user should be allowed to disable this feature just in case he or she wants to make sure the latest revision is always retrieved.
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
No files, tests, or entry points are named. Start by locating the client configuration retrieval path and determine how a filesystem cache and an explicit disable option should behave; done means clients can start without retrieval, reduce requests, and still retrieve the latest revision when caching is disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100