Because sometimes you want to cache pages for browsers that didn't visit
you yet? :) In other words, when I have a productpage that needs all
kinds of database lookup etc, but I know that the render outcome will be
the same for all uses that access it for the next couple of weeks, I
might want to avoid the database hits and processor power for rendering,
and just serve from a buffer of file.
Eelco
Michael Jouravlev wrote:
Eelco, why bothering doing the job which is already done by browser
vendors? Seems that currently only resources like images are marked
with cache-control headers, and the lifetime is fixed. What is it? One
hour? Page itself is not marked, but it is possible by pulling out the
response object and setting cache-control header directly.
I would prefer to have some automation and settings to it, instead of
building server-side cache.
But even now it is pretty usable, just mark expire time as a day
after, send page to browser, and voila, browser would cache page
off-server. Which is easier to implement, and cheaper memory-wize.
Anyway, who would like to cache pages for days? ;)
Michael
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
