spring-projects / spring-projects/spring-session
Add Documentation About Session Size
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.9k
- Forks
- 1.2k
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 55
Description
In general, users who are not distributing their session are probably already paying the cost of large sessions with memory consumption. However, the problem is likely to get worse when users can distribute the sessions easily. We should provide some documentation on what belongs in a session and what does not.
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
Start by reviewing the existing Spring Session documentation and identify where guidance on session contents belongs. Document what should and should not be stored in a session, including the memory implications of distributing sessions; done when users can find clear, actionable guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100