setCached causes wicket to send http cache headers. Resources it self are cached in SharedResources. The resource itself is responsable what is cached internally
On 9/17/07, Leszek Gawron <[EMAIL PROTECTED]> wrote: > Johan Compagner wrote: > > ahh ok that seems a bug can you report this? > > sure can, > > one last question: there is a method set/getCached(). Does this tell the > browser to cache the resource or does wicket cache it itself? > > -- > Leszek Gawron > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
