[ https://issues.jboss.org/browse/SHRINKWRAP-496?page=com.atlassian.jira.pl... ] Andrew Rubinger commented on SHRINKWRAP-496: -------------------------------------------- There be dragons here. :) While I can see sharing a cache scoped to a particular object, I wouldn't implement a cache in the ShrinkWrap API itself to be shared between objects. Especially in testing, calls should be idempotent so that each run of the test class does the same thing each time. Contents behind a URL can change over time, so if machine A and machine B have different caches at time X, they'll return different things. Of course a user is free to implement whatever Asset type they want and extend ShrinkWrap in that way. So +1 to some impl of UrlAsset which caches the content, but I would scope the cache to that object only. Pull requests welcome. Also, a version of this which uses a mem-based cache would be good too (basically wrapping ByteArrayAsset) -- This message was sent by Atlassian JIRA (v6.4.11#64026)