uNetworking / uNetworking/uWebSockets
Some caching features
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 19k
- Forks
- 1.9k
- Avg merge
- 3h 24m
- Merged PRs (30d)
- 5
Description
close - ideally it should be smarter but we can begin by simply rendering an error page in case the cache updating calls close. That's simple and solves this glaring issue.
writeHeader - simple fix, used everywhere
endWithoutBody - also relatively obvious
And we can add caching for more methods not just GET
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
Start by locating the cache-update handling for the named close, writeHeader, and endWithoutBody paths. Review how errors are rendered and how caching currently applies to GET, then define completion as safe error handling for failed cache updates and verified support for the requested methods.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100