Another possibility in Tap3 is to increase the lifetime of pages in the
pool.
// Each unit here is one half-minute, the default janitor cleanup
period.
// Pick a big number; 86,400 half-minutes is 30 days.
private static final int POOLED_PAGE_LIFETIME = 86400;
// Do this in some one-time place like engine.createGlobal() or
createVisit().
getPool().setWindow(POOLED_PAGE_LIFETIME);
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, September 06, 2005 3:21 AM
Subject: can I change the page pool?
> I would like to change the implementation of the page pool. The reason is
that the page pool after a while will release all instances of a page. Since
I am the only user of my own website and do not visit the pages that often I
end up always paying the construction-page-price. So I would like to have a
page pool that releases all instances but one for every page, or even
better, use soft references and let the JVM handle the cleanup :)
>
> For tapestry 3 (which I use now) I will have to change the source and
rebuild tapestry, but does anyone know if there is or will there be an
extension point in Tapestry 4 to change this?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
