I want this to be extremely transparent and easy (although more
configuration options could be available elsewhere if they are
truly needed).
One should be able to do this to any Wicket page and have it
and all its subclasses render on an interval:
/**
* @return Duration between renders of this page or null to always render
*
*/
protected Duration getRenderInterval()
{
return Duration.ONE_MINUTE;
}
And Page.getRenderInterval() would return null, of course.
The implementation could simply be to attach an object
to the page using the metadata facility which contains a
last rendered time and a buffer. If the page is asked to
render before the buffer has expired, it simply renders the
buffer as the response.
Jean-Baptiste Quenot-3 wrote:
>
> * Jonathan Locke:
>
>
>> Sounds good. And of course there's that earlier thread about
>> making it really easy to make a dynamic page render static
>> snapshots on an interval. That would also be particularly
>> interesting for certain applications.
>
> Indeed caching is the next step, and it is something badly needed
> in Wicket. I remember some weeks ago the developers arguing that
> we don't need ehcache, that makes sense if you only consider
> storing pages, but Wicket's page store is definitely not a
> general-purpose store.
> --
> Jean-Baptiste Quenot
> aka John Banana Qwerty
> http://caraldi.com/jbq/
>
>
--
View this message in context:
http://www.nabble.com/Serving-Static-Pages-with-Wicket-tf3572749.html#a9995177
Sent from the Wicket - Dev mailing list archive at Nabble.com.
