tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Created] (TAP5-2123) Compiled CoffeeScript and Less files should be cached in development mode
Date Fri, 31 May 2013 21:44:20 GMT
Howard M. Lewis Ship created TAP5-2123:
------------------------------------------

             Summary: Compiled CoffeeScript and Less files should be cached in development
mode
                 Key: TAP5-2123
                 URL: https://issues.apache.org/jira/browse/TAP5-2123
             Project: Tapestry 5
          Issue Type: Improvement
          Components: tapestry-wro4j
    Affects Versions: 5.4
            Reporter: Howard M. Lewis Ship


When any asset changes, all caches are (normally) discarded.

This isn't normally a major issue; Tapestry can re-read files, and repopulate its caches quickly.

However, CoffeeScript to JavaScript compilation can be quite slow ... reasonable sized files
may take 10 or 15 seconds to compile (when using the sluggish Rhino JavaScript VM). 

It makes sense, then, to cache those files differently; a cache that tracks the source resource
path and the checksum for the source resource and matches that to the compiled content stream.
After changing a single file, only that one file would actually have to be recompiled; all
the others would be served from the development-mode cache. The cost would be a quick scan
of the file contents to build a checksum, to determine if the file content has changed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message