yeah that's true in general . Good catch. However, I have a sessionid
strippping filter in place so it doesn't effect me luckily.
Andreas Andreou-4 wrote:
>
> As a note, one sideeffect i can think of would occur if the first
> user (when cache doesn't yet exist) has cookies disabled (and thu
As a note, one sideeffect i can think of would occur if the first
user (when cache doesn't yet exist) has cookies disabled (and thus
url-rewriting
takes place)...
in that case, the cache would be filled in with urls
containing his specific JSESSIONID, e.t.c.
On Wed, May 6, 2009 at 2:16 AM, Britsk
ok solved (don't know why I didn't see this earlier ;-)
simply tested in template if cached html existed.
if false --> render component
if true --> use OutputRaw to output cached html of component.
cheers,
Britske
Britske wrote:
>
> currently I'm working on a page with a lot of components.
ok, tried a couple of things, but none of them work:
1. in the container component keep track of the element that is created by
the container component.
in the afterRender fetch the html as element.toString() and put to cache.
in the beginrender method check the cache and if found --> write t
currently I'm working on a page with a lot of components.
part of these components are lists with contents related to the visitor
viewing the page (i.e: last viewed products, product in wishlist) but most
of these components display lists which are related to context of the page
only (and are thu
