[jira] [Closed] (TAP5-2318) Module responses uses paranoid max-age: 0, should be more liberal in production

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

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

Howard M. Lewis Ship closed TAP5-2318.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.4

> Module responses uses paranoid max-age: 0, should be more liberal in production
> -------------------------------------------------------------------------------
>
>                 Key: TAP5-2318
>                 URL: https://issues.apache.org/jira/browse/TAP5-2318
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>              Labels: cache
>             Fix For: 5.4
>
>
> Since module requests can-not contain a content checksum in the URL, they must be validated by the client frequently.
> In development, a max-age of 0 makes sense; there is no cost to checking the module's current status (modules include E-Tag headers) and a stiff cost to having the wrong code running in the browser during development.
> In production, the max-age of 0 causes a significant load on the origin server as even intermediate caches must pass a constant stream of requests through to the origin server for validation ... even for a user navigating from page to page within the application (rather than returning to the application hours or days later).
> Having max-age (and the other values) be configurable in production would be ideal; a max-age of several minutes to an hour would likely result in virtually no client-side failures.



--
This message was sent by Atlassian JIRA
(v6.2#6252)