uNetworking / uNetworking/uWebSockets.js
Cache invalidation use cases and interface
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 9.2k
- Forks
- 625
- Avg merge
- 6h 7m
- Merged PRs (30d)
- 13
Description
- Invalidate a URL
- Invalidate all URLs that a route handler could have taken
- All invocations of a cached route handler gets its own invalidator function passed in
Which one is most useful?
Contributor guide
No contributing guide indexed for this repository
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 reviewing the existing cache and route-handler interfaces, then compare the three invalidation options listed in the issue; done requires an agreed interface and behavior before implementation and tests can be defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, nodejs
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100