tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Canfield (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (TAP5-1489) Re-storage of session attributes at end of request should be configurable (can be set to off for non-clustered applications)
Date Sat, 02 Apr 2011 21:12:05 GMT

     [ https://issues.apache.org/jira/browse/TAP5-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Josh Canfield reassigned TAP5-1489:
-----------------------------------

    Assignee: Josh Canfield

> Re-storage of session attributes at end of request should be configurable (can be set
to off for non-clustered applications)
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1489
>                 URL: https://issues.apache.org/jira/browse/TAP5-1489
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.3.0, 5.2.5
>            Reporter: Howard M. Lewis Ship
>            Assignee: Josh Canfield
>            Priority: Minor
>
> 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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message