You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/01/08 06:06:44 UTC
[jira] Assigned: (TAP5-90) Context assets should be versioned and
provided with a far future expires header, just like classpath assets
[ https://issues.apache.org/jira/browse/TAP5-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-90:
----------------------------------------
Assignee: Howard M. Lewis Ship
> Context assets should be versioned and provided with a far future expires header, just like classpath assets
> ------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-90
> URL: https://issues.apache.org/jira/browse/TAP5-90
> Project: Tapestry 5
> Issue Type: New Feature
> Affects Versions: 5.0.15
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> This is as-per YSlow recommendations, assets in the context (i.e., the context: asset prefix) should be treated like classpath: assets; the URL sent to the browser should reflect a version number (defined by the application) and the files should be given a far future expiration date.
> So the URL might be "/app-assets/1.2.3/images/logo.gif" for a file referenced as "context:images/logo.gif". The application would define the version number. It would be the developer's responsibility to advance the version number whenever the context files change (i.e., on each new deployment of the application).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org