[
https://issues.apache.org/jira/browse/TAP5-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAP5-2134.
--------------------------------------
Resolution: Invalid
Just looked at the code, and symbol tapestry.session-locking-enabled exists for
this purpose.
> Session locking (introduced in 5.4) should be optional
> ------------------------------------------------------
>
> Key: TAP5-2134
> URL: https://issues.apache.org/jira/browse/TAP5-2134
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Yunhua Sang
> Assignee: Howard M. Lewis Ship
> Labels: thread-safety
> Attachments: TestPage.java, TestPage.tml
>
>
> Tapestry 5.4 introduced session locking, whereby access to the HttpSession is
> serialized when multiple threads are active for the same session (this can
> occur in some Ajax scenarios). This has been highly controversial, and (at
> the very least), it should be optional, controlled by a configuration symbol.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
