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 > > Eelco Hillenius wrote: > > > >> Hi, > >> > >> The markup is cached anyway. You probably want the results cached. > >> > >> There's tons of ways to do it, the most obvious ones being: > >> - using a seperate cache, e.g. implemented as a servlet filter. I've > >> used http://www.opensymphony.com/oscache/ for this in the past. If > >> you only have to cache bookmarkable pages (and actually caching > >> non-bookmarkable pages is not a good idea as they need session > >> state), that works quite good. > >> - generate static HTML. Many large sites just generate their whole > >> catalogue etc to static html files. You can't get better performance/ > >> scalability than that. So, if you work on a really large scale site, > >> that might be an option. > >> > >> Above two ways are not integrated with Wicket. We could consider > >> building in native support for caching, but as caching (at least the > >> kind of caching we're talking about here) spans multiple sessions, it > >> would not be a straight match with Wicket's design goals. > >> > >> Eelco > >> > >> > >> Christian Essl wrote: > >> > >>> Hi, > >>> > >>> My most used pages are product-catalog and product-detail. Both > >>> pages are and should be bookmarkable. The product-catalog page uses > >>> a ListView to show all products in a category. The detail pages uses > >>> a form to add the prodcut to the shopping-basket: > >>> > >>> Because the products do change only about every second week I want > >>> to cache the markup for both pages (or better the actual panels > >>> which show the products). > >>> > >>> Is this possible in Wicket? > >>> > >>> Thanks, > >>> Christian ------------------------------------------------------- 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_idt77&alloc_id492&op=click _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
