Skip to content

Consider moving away from Java serialization as default serialization mechanism #1913

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
vpavic opened this issue Sep 7, 2021 · 0 comments
Labels
type: breaks-passivity This issue breaks passivity type: enhancement A general enhancement
Milestone

Comments

@vpavic
Copy link
Contributor

vpavic commented Sep 7, 2021

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.

@vpavic vpavic added type: enhancement A general enhancement status: waiting-for-triage An issue we've not yet triaged type: breaks-passivity This issue breaks passivity labels Sep 7, 2021
@vpavic vpavic added this to the 3.x milestone Sep 7, 2021
@eleftherias eleftherias removed the status: waiting-for-triage An issue we've not yet triaged label Sep 27, 2021
@eleftherias eleftherias modified the milestones: 3.x, 3.0.0-M1 Nov 12, 2021
@rwinch rwinch removed this from the 3.x milestone Nov 15, 2022
@marcusdacoregio marcusdacoregio added this to the 4.0.0-M1 milestone Dec 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: breaks-passivity This issue breaks passivity type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

4 participants