Explicitly set session attribute at the end of UI/session access to support clustering
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 717
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 3
Description
Originally by @hesara
Some clustering solutions such as the default Tomcat clustering valve replicate information in a cluster based on HttpSession attributes that are explicitly set during the processing of a request. Therefore, Vaadin should explicitly mark which sessions have been touched so that the clustering solution does not need to try to track those with extra listeners or aggressively replicate everything.
Imported from https://dev.vaadin.com/ issue #19648
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 tracing the UI/session access lifecycle and how HttpSession attributes are handled during a request. Verify where session access ends and how an explicit attribute update would signal that the session was touched for clustering; done means the behavior is covered and compatible with the reported Tomcat clustering use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100