AssetSource should use more aggresive caching
---------------------------------------------
Key: TAP5-970
URL: https://issues.apache.org/jira/browse/TAP5-970
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.2.0
Reporter: Howard M. Lewis Ship
Priority: Minor
I'm increasingly finding myself writing code that uses AssetSource to obtain
assets on-the-fly as part of a component's rendering. Looking at the code,
this does not appear to be exceptionally efficient, as Resources (along with
the associated disk file I/o) must be created and localized before a (cached)
Asset instance can be identified.
A memoization approach, where method names and method parameters to AssetSource
are used to as a cache key, should yield better performance.
As I remember, there was a discussion on the mailing list about too much time
being spent inside AssetSource.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
