Skip to content

Support heterogeneous spring session version in client / server topology #1312

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.

Sign up for GitHub

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

Jump to bottom
Closed
dougkei opened this issue Jan 14, 2019 · 6 comments
Closed

Support heterogeneous spring session version in client / server topology #1312

dougkei opened this issue Jan 14, 2019 · 6 comments
Assignees
@vpavic
Labels
status: duplicate A duplicate of another issue

Comments

@dougkei
Copy link

dougkei commented Jan 14, 2019 •
edited
Loading

Suggest to customized serialization of SessionUpdateEntryProcessor such that single hazelcast server cluster can serve clients of different spring session versions (e.g. 1.3.5, 2.0.8 and 2.1.3) concurrently.
Suggested approaches:

  • SessionUpdateEntryProcessor to implement Portable
  • build StreamSerializer for SessionUpdateEntryProcessor
  • SessionUpdateEntryProcessor to provide public getter/setter methods so consumer can build their own serialization mechanism as above
@vpavic vpavic self-assigned this Jan 15, 2019
@vpavic
Copy link
Contributor

vpavic commented Jan 15, 2019 •
edited
Loading

Thanks for the suggestion @dougkei - we already have #1131 to handle some serialization related improvements. Can you add your comments over there? I think we even might consider this one as duplicate since all those improvements could be implemented together.

@vpavic vpavic added the status: waiting-for-feedback We need additional information before we can continue label Jan 15, 2019
@veereshwaran

This comment has been minimized.

Sign in to view
@vpavic

This comment has been minimized.

Sign in to view
@veereshwaran

This comment has been minimized.

Sign in to view
@michaelhaessig michaelhaessig mentioned this issue Jan 18, 2019
Closed
@vpavic
Copy link
Contributor

vpavic commented Jan 28, 2019

I'm going to close this one as duplicate of #1131.

@vpavic vpavic closed this as completed Jan 28, 2019
@vpavic vpavic added status: duplicate A duplicate of another issue and removed status: waiting-for-feedback We need additional information before we can continue labels Jan 28, 2019
@vpavic
Copy link
Contributor

vpavic commented Jan 28, 2019

Duplicate of #1131

@vpavic vpavic marked this as a duplicate of #1131 Jan 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vpavic vpavic

Labels
status: duplicate A duplicate of another issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@vpavic @veereshwaran @dougkei