[jira] [Closed] (TAP5-970) AssetSource should use more aggresive caching

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-970.
-------------------------------------

    Resolution: Won't Fix

> 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
>            Reporter: Howard M. Lewis Ship
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)