There is an assertion in AWDWR that the in-memory session store is “too
However, I find myself nudged in this direction by the need to keep a
non-serializable model attribute available in my session and the
relative pain of implementing either a custom serialization scheme for
the model in question (or a custom caching mechanism so that I can store
my attribute in memory).
When I first read that the in - memory storage method was frowned upon,
I was surprised, because in my experience, only some e-commerce shopping
cart apps sometimes handle session persistence.
Anyone have any thoughts on the validity of using an in-memory session
Obviously, it’s much faster as well.