[TAP5-2123] Compiled CoffeeScript and Less files should be cached in development mode

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 5.4
• Component/s: tapestry-webresources
• Labels: caching coffee-script development-mode
• Assignee: Unassigned
• Reporter: Howard Lewis Ship
• Created: 31/May/13 21:43
• Updated: 24/Dec/14 01:26
• Resolved: 24/Dec/14 01:26

Description

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.