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 Improvement
    • Status: Closed
    • Priority: Minor 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.

        Activity

        Howard M. Lewis Ship created issue -
        Josh Canfield made changes -
        Field Original Value New Value
        Assignee Josh Canfield [ joshcanfield ]
        Josh Canfield made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Josh Canfield made changes -
        Status In Progress [ 3 ] Resolved [ 5 ]
        Fix Version/s 5.3.1 [ 12316673 ]
        Resolution Fixed [ 1 ]
        Howard M. Lewis Ship made changes -
        Affects Version/s 5.3 [ 12316024 ]
        Affects Version/s 5.3.0 [ 12316023 ]
        Howard M. Lewis Ship made changes -
        Fix Version/s 5.3 [ 12316024 ]
        Fix Version/s 5.3.1 [ 12316673 ]
        Howard M. Lewis Ship made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development