[TAP5-1489] Re-storage of session attributes at end of request should be configurable (can be set to off for non-clustered applications)

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.3, 5.2.5
• Fix Version/s: 5.3
• Component/s: tapestry-core
• Assignee: Josh Canfield
• Reporter: Howard Lewis Ship
• Created: 29/Mar/11 23:42
• Updated: 17/Aug/11 22:12
• Resolved: 25/Jun/11 12:38

Description

It's great that Tapestry has the re-storage logic built in, but it's only necessary to deal with a gap in how replicated sessions are synchronized across nodes of a cluster. In the more typical case, Tapestry is being used in a single node (no cluster), or using sticky sessions with no session replication, and the extra work of analyzing and re-storing attributes is not necessary.

It should default on; users should have to explicitly disable the support.