spring-projects / spring-projects/spring-session
Consider moving away from Java serialization as default serialization mechanism
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.9k
- Forks
- 1.2k
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 55
Description
At present, all SessionRepository implementations use Java serialization as the default serialization mechanism.
While convenient as a default, Java serialization has several well known limitations and the ecosystem appears to be getting ready to move away from it - see Towards Better Serialization document by Brian Goetz.
The next major release seems like a good opportunity to reconsider Spring Session's general approach to serialization.
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 SessionRepository implementations and the linked OpenJDK “Towards Better Serialization” document. Determine which serialization alternatives and compatibility requirements Spring Session would need before changing the default. Done would require an agreed general serialization approach for the next major release, including its migration impact.
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