Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: domain of max.pfingsthorn@gmail.com
 designates 64.233.166.182 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Rm/Zx798JVR/6kqNhfGaFeLke3zjDgu5Ozo7ALjoNu0+uDoh1OXWqAVPkIN4UMCBn9iL/up7Q4/GsmamV7LlplALpaV7uy34dcmvqvK0WTK2j+/yAJI3CLgQN3tMom/5e5JFFXcHG3l5BZmJMhNYS7svLMWFbYFx5GE1AEk4iPg=
Message-ID: <25335d770603160814o76514b7chba37d222622dea3b@mail.gmail.com>
Date: Thu, 16 Mar 2006 17:14:37 +0100
From: "Max Pfingsthorn" <max.pfingsthorn@gmail.com>
To: users@cocoon.apache.org
Subject: Re: is it possible to cache sql queries?
In-Reply-To: <A955EA1F8FE31749AEC8C998082F6C7CBA8844@hai01.hippo.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <A955EA1F8FE31749AEC8C998082F6C7CBA8844@hai01.hippo.local>

Hi!

I've just committed it. Please test it a little. I did a little stress
test with a pipeline that did an aggregate of around 100 parts
directly from the filesystem and serialized it to xml. The cached
response took 0-16 ms, while generating it took over 500 ms.

Be aware that the default cache key for all pipelines is the exact uri
you used to generate it. This has always been so with the
ExpiresCachingProcessingPipeline.
If you need to write your own (maybe your pipeline also depends on
session attributes or request parameters), use it like this:

<map:pipeline type=3D"expires">
  <map:parameter name=3D"cache-key"
value=3D"mycachekey-{0}-{request-param:myparam}-{session-attr:myattr}"/>

  <map:match pattern=3D"bla">
    ...
  </map:match>
</map:pipeline>

Then the cache key will be of the same form for _all_ matchers within
this block. If you need another form (i.e. add/remove parameters), you
need to declare a nother pipeline element and give it a new
"cache-key" parameter.

By the way, "{0}" gives you the complete uri the matcher matched.

Have fun!
max

On 3/16/06, Ard Schrijvers <a.schrijvers@hippo.nl> wrote:
>
> > Derek Hohls wrote:
> > > Any chance this will be in the forthcoming 2.1.9 release?
> >
> > I'm sat next to Ard right now so with a bit of luck, yes ;-)
> >
>
> Max is committing it. Should be available in 2.1.9
>
> AS
>
> --
>
> Hippo
> Oosteinde 11
> 1017WT Amsterdam
> The Netherlands
> Tel  +31 (0)20 5224466
> -------------------------------------------------------------
> a.schrijvers@hippo.nl / http://www.hippo.nl
> --------------------------------------------------------------
>
>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org