Details
-
Improvement
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
None
-
None
-
None
Description
Session refreshes are quite expensive in a clustered environment. At the same time, the only way to flush virtual states from a jcr session (without calling save()) is a session#refresh
The HST uses session pools, which can contains tens to hundreds of jcr sessions. These session mainly contain virtual states.
After any change below /content, the only thing the HST can do is refresh all its sessions in its most common session pools. However, it would already be sufficient if it could just flush its virtualstates.
Hence, we'd like to be able to call something like:
HippoSession#disposeVirtualStates()
Then, we just flush the virtual states, which is in general enough for our read only hst session pools afaics
Attachments
Issue Links
- is awaited by
-
HSTTWO-1976 Abstract the pooled jcr session refresh into a pluggable mechnism, to be able hook in different refreshing calls later, for example one that only disposes virtual session states
- Closed
-
HSTTWO-2006 Dispose Virtual States option only via HippoSession#disposeVirtualStates() in the session pool when content change events triggered
- Closed
- relates to
-
HSTTWO-1976 Abstract the pooled jcr session refresh into a pluggable mechnism, to be able hook in different refreshing calls later, for example one that only disposes virtual session states
- Closed