<div dir="ltr"><font color="#330033"><font size="2"><font face="tahoma,sans-serif">Phillipe,<br>re query parameters - obviously, but aren't the seaside params (_k,_s) get new values each time the page is rendered?<br>re component caching - why we don't want to go this way?<br>
<br>About your comment about the database layer - I disagree. Navigational elements can be cached, without the need to call the render chain. I think it is valuable to have components' output cached.</font></font></font><br>
<div style="margin: 2em 0pt;" name="sig_d41d8cd98f">Cheers,<br>
Avi.</div><div class="gmail_quote">On Sun, Mar 13, 2011 at 12:34 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/7 Avi Shefi <<a href="mailto:avishefi@gmail.com">avishefi@gmail.com</a>>:<br>
<div class="im">> Hi all,<br>
> I've taken the time to implement issue 435 and encountered some issues.<br>
><br>
> 1. I have created a caching filter which caches the response according to<br>
> the request URL using WACache. It uses the request url without the query<br>
> params (i.e. aRequestContext request url withoutQuery). This causes problems<br>
> however with WAComponent>>#script, which uses the same URL (without query<br>
> params) and therefore serves the content of the page (instead of the<br>
> contents of the #script method). Any suggestions how to solve this?<br>
<br>
</div>Include the query parameters in the cache key as well?<br>
<div class="im"><br>
> 2. I think it's also important to provide component caching,<br>
<br>
</div>I don't think we wanna go there.<br>
<div class="im"><br>
> so that<br>
> individual components can be cached. (Rational: navigation components that<br>
> pull data from databases should be cached, instead of generated each time)<br>
<br>
</div>That should be the responsibility of the database layer (ie. Glorp) or<br>
business layer but not the GUI layer (Seaside).<br>
<div class="im"><br>
> I<br>
> guess the way to do this is to add a decoration around a component, and use<br>
> that as a cache for the component's contents. However, the contents of the<br>
> component is inserted through a canvas, which writes its contents directly<br>
> to the returned document. We can use an additional document and get its<br>
> output specifically for the component caching, however this feel a bit<br>
> awkward. Any other ideas how to get a component's output so it can be<br>
> cached?<br>
<br>
Cheers<br>
</div>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>
</blockquote></div><br></div>