<div dir="ltr"><font color="#330033"><font size="2"><font face="tahoma,sans-serif">Well, if we can't cache the #script element, then we can't cache using query params (_k and _s keep changing).<br>I implemented caching of a request handler, however #script and #style should be left out of this (as they cannot be differentiated from the page itself). But then again, when we use forms and call:answer: , the URL never changes, only _k and _s change. So we can't cache anything.<br>
</font></font></font><font color="#330033"><font size="2"><font face="tahoma,sans-serif">So.. where how do we continue on <a href="http://code.google.com/p/seaside/issues/detail?id=435">issue 435</a>? Is there any point of having page cache if we can't differentiate between pages?<br>
<br></font></font></font><font color="#330033"><font size="2"><font face="tahoma,sans-serif"><br>About component caching - it seems logical to me, however since Seaside relies on components all the way, this one is far-fetch.</font></font></font><br>
<div style="margin: 2em 0pt;" name="sig_d41d8cd98f">Cheers,<br>
Avi.</div><div class="gmail_quote">On Tue, Mar 15, 2011 at 5:31 PM, Philippe Marschall <span dir="ltr"><<a href="mailto:philippe.marschall@gmail.com">philippe.marschall@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
2011/3/14 Avi Shefi <<a href="mailto:avishefi@gmail.com">avishefi@gmail.com</a>>:<br>
<div class="im">> Phillipe,<br>
> re query parameters - obviously, but aren't the seaside params (_k,_s) get<br>
> new values each time the page is rendered?<br>
<br>
</div>Yes. And they render differently every time that's why we can't cache<br>
applications.<br>
<div class="im"><br>
> re component caching -<br>
> why we don't want to go this way?<br>
<br>
</div>I have seen where this leads with jsp tag and stateful session bean<br>
caching, and the fundamental problems are the same. In addition<br>
creating new components has never been a problem.<br>
<div class="im"><br>
> About your comment about the database layer - I disagree. Navigational<br>
> elements can be cached, without the need to call the render chain.<br>
<br>
</div>But why? It has never been a performance problem.<br>
<div class="im"><br>
> I think<br>
> it is valuable to have components' output cached.<br>
<br>
</div>I think that's too complicated. The output may depend on the state of<br>
the component and many other times like the current time.<br>
<div><div></div><div class="h5"><br>
Cheers<br>
Philippe<br>
_______________________________________________<br>
seaside-dev mailing list<br>
<a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
</div></div></blockquote></div><br></div>