XML caching

[Roel van Dijk <rd...@gmail.com>]

After developing a Jetspeed 1.6 portal for a few months, I've now been
optimizing it for the production environment (a few thousand users).

I've run into a problem concerning the caching of portlets and their
content. I've created a few XSL Portlets using XML feeds available on
our network, and would like to optimize caching of the XML in these
portlets. I've found these properties in the
JetspeedResources.properties file:

daemon.diskcachedaemon.interval=
cache.default.expiration=

For example, if I would like my portlets to refresh their XML content
really quickly, let's say 10 seconds, I have to set _both_ these
properties to 10. Setting either one to a higher value, the portlet
content is refreshed until that many seconds have elapsed. Naturally,
these properties also influence other parts of the portal apart from
the XML caching.

So here's my question: can an XSL Portlet's content (the XML) have a
specific caching time which does not influence other parts of the
system?

Thanks for any tips,
-- 
Roel -- rdvdijk@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org

Re: XML caching

[David Sean Taylor <da...@bluesunrise.com>]

Roel van Dijk wrote:
> After developing a Jetspeed 1.6 portal for a few months, I've now been
> optimizing it for the production environment (a few thousand users).
> 
> I've run into a problem concerning the caching of portlets and their
> content. I've created a few XSL Portlets using XML feeds available on
> our network, and would like to optimize caching of the XML in these
> portlets. I've found these properties in the
> JetspeedResources.properties file:
> 
> daemon.diskcachedaemon.interval=
> cache.default.expiration=
> 
> For example, if I would like my portlets to refresh their XML content
> really quickly, let's say 10 seconds, I have to set _both_ these
> properties to 10. Setting either one to a higher value, the portlet
> content is refreshed until that many seconds have elapsed. Naturally,
> these properties also influence other parts of the portal apart from
> the XML caching.
> 
> So here's my question: can an XSL Portlet's content (the XML) have a
> specific caching time which does not influence other parts of the
> system?
> 
Yes.
However the XSLT portlet does not use the diskcachedaemon.
As with all portlets that inherit from AbstractPortlet, you must set the 
expiration on this portlet in milliseconds programmatically (perhaps in 
the init)

setExpirationMillis(long ms)

-- 
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
[office] +01 707 773-4646
[mobile] +01 707 529 9194

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org