Read and respond to this message at:
I can think of several reasons why you wouldn't want to cache a portal page
but in this particular case I was wondering if there was any technical reasons
why it should be disabled. In the past I've come across CCM apps that require
caching to be disabled to work correctly, e.g. needed a new set of objects to
be created per request or you'd get some odd behaviour.
If you grep through the APLAWS+ source, most of the JSP pages disable caching,
which makes you wonder, why? I suspect that most of them can be cached, it's
just no one has tested it yet.
The portal page I'm using is fairly static so I'll turn on caching and see what
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: