Feature #138
Tapestry page pooling
| Status: | Rejected | Start: | 19/01/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: |  Raphael Ouazana |
% Done: | 0% |
|
| Category: | WUI | Spent time: | - | |
| Target version: | 2.0 |
Description
Since Tapestry 5.2, Tapestry doesn't pool pages anymore. So only one instance of each page (per locale) is loaded.
This can cause many concurrency and maybe security issues, so this must be tested intensively.
If there are too many bugs related, page pooling can be reactivated.
History
Updated by Raphael Ouazana 3 months ago
- Assigned to set to Raphael Ouazana
- Status changed from New to Rejected
The complete explanation can be founded here: http://tapestryjava.blogspot.com/2010/07/everyone-out-of-pool-tapestry-goes.html
So it seems this is only an internal change that should not affect LinID DM.