<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Achim,<br>
<br>
Am 06.07.2013 18:44, schrieb Achim Westermann:<br>
</div>
<blockquote cite="mid:51D85797.90105@gmx.de" type="cite">
<pre wrap="">Hi Tobias,
</pre>
<blockquote type="cite">
<pre wrap="">What about the attribute "cacheable" of the cms:include-Tag?
So far we used cms:include to include parts of a page which mustn't be
cached... worked very well with 7.5.4.
If this isn't working any more it's preferable to use static includes,
because they're much more faster.
</pre>
</blockquote>
<pre wrap="">There is nothing about cache "not working any more". That part of
OpenCms is pretty deep-down, stable and untouched. I am not writing that
from my current knowledge but from my experience with OpenCms. But my
"feeling" tells me that this issue is worthwhile to dig deeper why
something in your webapp did work and now does not. As opposed to say
"It worked in 7.5.4, in 8 it does not. So the latest version has issues."
Static includes are not faster if you want to use caching. Those will
not make use of any caching at all but be included in the jsp
compilation phase. Think of a jsp that performs heavy database
operations being included statically: That code will get executed for
every call.
OK, static includes are faster, if you do not want to cache at all. But
do you want that? You can even set the OpenCms cache to have a timeout
in minutes. Pretty mighty. It is worth spending some time on the OpenCms
cache setting. Cache is king. Dropping caching may only work if you buy
faster hardware. And may always be compromised by the intensity of DOS
attacks.
</pre>
</blockquote>
Thanks for yopur answer.<br>
I agree complete "Cache is king". But still there are pages or parts
of pages, which you don't want to be cached, and I'm looking for a
good way to exclude thes parts from caching.<br>
<br>
I meanwhile did different tests with cms:includes, to see why the
different behaviour occurs.<br>
Finally: there has been a small change, so the cache-setting for a
session attibute behaves a little different. In some especial
circumstances the problem will have occured in 7.5.4 as well. So not
the updateto Version 8 itself was responsible.<br>
<br>
<blockquote cite="mid:51D85797.90105@gmx.de" type="cite">
<blockquote type="cite">
<pre wrap="">Or what to do to exclude parts of a page from caching?
</pre>
</blockquote>
<pre wrap="">
Set property cache to "never" on a jsp. And then be flexible to decide
to cache the output of that jsp later on properly.
</pre>
</blockquote>
Clearly, but what if this jsp includes other jsps, which I don't
want to be cached.<br>
<br>
Example:<br>
/mysite/dynamic-include.jsp (cache=never) with "Time in Millis:
<%= <code>System.currentTimeInMillis() %></code>"<br>
/mysite/page.jsp (cache=uri) which contains "<cms:include
cacheable="false" file="/mysite/dynamic-include.jsp"/>"<br>
<br>
With the first call of "/mysite/page.jsp" both pages are compiled an
the final HTML-Markup ends up in the FlexCache.<br>
For the second call the whole page will be delivered by FlexCache.
Time in Millis always will be the compilation time (until FlexCache
is purged)<br>
<br>
Or am I wrong?<br>
<br>
Greeting,<br>
Tobias<br>
</body>
</html>