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

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

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

Jochen Kemnade updated TAP5-970:
--------------------------------

    Labels: bulk-close-candidate  (was: )

This issue has been last updated about 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent development preview of Tapestry (5.4-beta-6, which is available from Maven Central), please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org mailing list first.


> 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)