Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-1489

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

    Details

    • 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
    • Labels:
      None

      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.

        Attachments

          Activity

            People

            • Assignee:
              joshcanfield Josh Canfield
              Reporter:
              hlship Howard M. Lewis Ship
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: