You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2014/07/25 10:56:38 UTC

[jira] [Comment Edited] (TAP5-2325) Minification cache warming

    [ https://issues.apache.org/jira/browse/TAP5-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14074213#comment-14074213 ] 

Jochen Kemnade edited comment on TAP5-2325 at 7/25/14 8:54 AM:
---------------------------------------------------------------

That code will not work anymore with -beta-14 or later: TAP5-2139 / {{accbb5374aa29333d2a666d4225c66a77b56581f}} requires that a {{Request}} be available when acquiring a {{StreamableResource}}.


was (Author: jkemnade):
That code will not work anymore with -beta-14 or later: TAP5-2139 / {{accbb5374aa29333d2a666d4225c66a77b56581f}} requires a {{Request}} to be available when acquiring a {{StreamableResource}}.

> Minification cache warming
> --------------------------
>
>                 Key: TAP5-2325
>                 URL: https://issues.apache.org/jira/browse/TAP5-2325
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Jochen Kemnade
>            Priority: Minor
>
> It should be possible to configure that certain resources that should be minified during the application startup, the rationale being that it can take some time to minify large assets and that can lead to timeouts in requirejs when the resource is requested for the first time.



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