gin-contrib / gin-contrib/cache
Why make CachePage public?
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 456
- Forks
- 100
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 2
Description
CachePage doesn't insure thread safe. In the high concurrency scenario, CachePage will make response data chaos.
I think CachePageAtomic is the only right choice. Why don't make CachePage private directly?
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 CachePage and CachePageAtomic in the repository and reading how each is exposed and used. Inspect the concurrency assumptions described in the issue, then determine whether the public API should change; done requires a maintainer-approved resolution to the CachePage visibility and thread-safety concern.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100