On Thu, 18 Nov 2010 08:33:34 -0500 [email protected] wrote: > Right, good to know, was just providing the objects, assumed > implementation of render to be irrelevant, but I guess not entirely. > Anyway, I'm also interested in the second part of your question, what > does resource.setCacheable(false) effect, I've had trouble tracking > this down in the resource classes...
Right now, the cacheable flag just controls the headers sent to the browsers - they either are set as being cacheable, or not (must-revalidate). This goes for all Resource implementations. RenderedDynamicImageResource however caches the image data in an object field. Even when the browser comes along with another request, it will receive the same image again. Carl-Eric www.wicketbuch.de --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
