[Seaside-dev] [Seaside] Requests & Components Caching
avishefi at gmail.com
Tue Mar 15 17:08:52 UTC 2011
Well, if we can't cache the #script element, then we can't cache using query
params (_k and _s keep changing).
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.
So.. where how do we continue on issue
Is there any point of having page cache if we can't differentiate between
About component caching - it seems logical to me, however since Seaside
relies on components all the way, this one is far-fetch.
On Tue, Mar 15, 2011 at 5:31 PM, Philippe Marschall <
philippe.marschall at gmail.com> wrote:
> 2011/3/14 Avi Shefi <avishefi at gmail.com>:
> > Phillipe,
> > re query parameters - obviously, but aren't the seaside params (_k,_s)
> > new values each time the page is rendered?
> Yes. And they render differently every time that's why we can't cache
> > re component caching -
> > why we don't want to go this way?
> I have seen where this leads with jsp tag and stateful session bean
> caching, and the fundamental problems are the same. In addition
> creating new components has never been a problem.
> > About your comment about the database layer - I disagree. Navigational
> > elements can be cached, without the need to call the render chain.
> But why? It has never been a performance problem.
> > I think
> > it is valuable to have components' output cached.
> I think that's too complicated. The output may depend on the state of
> the component and many other times like the current time.
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside-dev