[Seaside-dev] Re: [Seaside] Requests & Components Caching

[Avi Shefi]

Anybody?

On Mon, Mar 7, 2011 at 11:45 PM, Avi Shefi <avishefi at gmail.com> wrote:

> Hi all,
> I've taken the time to implement issue 435 and encountered some issues.
>
> 1. I have created a caching filter which caches the response according to
> the request URL using WACache. It uses the request url without the query
> params (i.e. aRequestContext request url withoutQuery). This causes problems
> however with WAComponent>>#script, which uses the same URL (without query
> params) and therefore serves the content of the page (instead of the
> contents of the #script method). Any suggestions how to solve this?
>
> 2. I think it's also important to provide component caching, so that
> individual components can be cached. (Rational: navigation components that
> pull data from databases should be cached, instead of generated each time) I
> guess the way to do this is to add a decoration around a component, and use
> that as a cache for the component's contents. However, the contents of the
> component is inserted through a canvas, which writes its contents directly
> to the returned document. We can use an additional document and get its
> output specifically for the component caching, however this feel a bit
> awkward. Any other ideas how to get a component's output so it can be
> cached?
>
>
> Cheers,
> Avi.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20110313/dca87ea1/attachment.htm