Do I need to call setAttribute() for every change if I use Spring Session? -
i in progress of migrate spring mvc + hibernate based application clustered environment (tomcat clustering). researching on possible solutions session replication / sharing. terracotta documentation
all clustered session implementations (including terracotta sessions) require mutated session object put session after it's mutated. if call missing, change isn't known cluster, local node. example:
session session = request.getsession(); map m = session.getattribute("foo"); m.clear(); session.setattribute("foo", m); // without call, clear() not effective across cluster.
just want know if same rule holds true spring session? mean spring session project
anyone knows reason behind rule? because when method called, spring session or terracotta web session serialize attribute object? without call, don't know object has changed? i.e. won't monitor object changes?
do know clustering solution don't have rule?
Comments
Post a Comment