Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Implemented
-
None
-
None
Description
Since Tapestry 5's inception, it throws the whole set of assembled page instances when anything related is changed, be it the class itself, its template and maybe also associated messages and assets. In very large projects with large pages, this can reach a point it slows down the user (programmer) productivity, forced to wait for unchanged pages to be reassambled.
Tapestry should provide some way for users to segment page, component, mixin and base classes to separate regions, one for each classloader, to avoid clearing out cached page instances that don't have themselves or the classes they use changed.