Add useEntryProcessor flag into HazelcastIndexedSessionRepository to avoid using remote user code deployment

[shustinho]

Expected Behavior

We should have a choise for session replication in HZ whether we want to execute code on client side or on cluster member. Add useEntryProcessor flag into HazelcastIndexedSessionRepository and do non atomic map.get(), map.put() in case of useEntryProcessor is false. Change should be made here HazelcastIndexedSessionRepository#save

Current Behavior

Right now client should provide classes to HZ member for remote execution. But simple http session replication is litghweight operation that can be executed on client side. Remote code deployment lead to a lot of restrictions and should be made by a valuable reason.

Context
So client couple with HZ instance and require the same JDK version as a minimum. I am not sure about difference spring versions.

[marcusdacoregio]

Hi, @shustinho. Thanks for the suggestion.

Do you mean that if the flag is false we should do something like:

this.sessions.set(session.getId(), session.getDelegate(), session.getMaxInactiveInterval().getSeconds(),
					TimeUnit.SECONDS);

instead of using the EntryProcessor do apply the update?

[shustinho]

Yes, @marcusdacoregio

[marcusdacoregio]

I think this is a duplicate of #1131. If we improve the serialization mechanism by using Portable, for example, we wouldn't need to add a flag to control the strategy used for session updates. Maybe we can add such an implementation in #1174 and port it to the servlet version.

That said, I will close this as a duplicate of #1131.