DURDINA Michal wrote:
I checked Pluto 1.0.1-rc1 (and also trunk) and the result is: pluto portal
(/portal) does not implement caching yet. The portlet.xml expiration-cache element
is parsed in PortletDefinitionImpl but never read (checked with Eclipse ->
References). The same is valid for cocoon
DURDINA Michal wrote:
I checked Pluto 1.0.1-rc1 (and also trunk) and the result is: pluto portal
(/portal) does not implement caching yet. The portlet.xml expiration-cache element
is parsed in PortletDefinitionImpl but never read (checked with Eclipse ->
References). The same is valid for cocoon
> -Original Message-
> From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 07, 2005 5:46 PM
> To: dev@cocoon.apache.org
> Subject: Re: ANN: [portal] New CachingPortletAdapter
>
>
> DURDINA Michal wrote:
> > Sorry for just a quick respo
DURDINA Michal wrote:
Sorry for just a quick response.
JSR168 - portlet specification really defines something like "expiration cache", which when set to -1 should provide caching of portlet content.
But as I see it:
* according to spec, implementation of caching is optional for portlet
contain
gate pluto distribution wheter caching is supported by pluto
container at all
Michal
> -Original Message-
> From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 07, 2005 1:14 PM
> To: dev@cocoon.apache.org
> Subject: Re: ANN: [portal] New CachingPortletAda
Hi,
the portlet standard already supports caching; each portlet can be
configured to be cached and the portlet container (in our case pluto)
should cache the content.
So I think our portal already does the caching. Or do I oversee something?
Carsten
DURDINA Michal wrote:
Hi,
after some days of co
