Wow that's what I call an elaborated response. Thanks a lot.
I'll try option C (labels). I plan to only cache the static part including
bookmarkable links and keep the rest normal Wicket. I will create the
static part using some templating-lib - maybe later use an extra Wicket
page, but I have
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eelco
Hillenius
Sent: Thursday, July 14, 2005 5:02 PM
To: wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] Caching components generated markup
Christian Essl wrote:
> Hi Eelco,
>
> Thanks for you reply. I have two more question
Christian Essl wrote:
Hi Eelco,
Thanks for you reply. I have two more questions.
In case of static pages: I am not sure how this works together with
the rest of wicket. The pages contain also a login, search and
add-to-shopping-basket from. How do I create for static pages the
sepecial wick
Hi Eelco,
Thanks for you reply. I have two more questions.
In case of static pages: I am not sure how this works together with the
rest of wicket. The pages contain also a login, search and
add-to-shopping-basket from. How do I create for static pages the sepecial
wicket-urls?
In my special
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
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 s
I do have pretty good experience with caching (no problems with expired
images etc here), though I agree that it certainly not allways is worth
the effort. But especially the generation of static pages (or maybe
combined static parts and a cach) can get drastic results. But it is
probably you h
I learnt very quickly that servlet-layer caching is a no go, at least
for me.
All the server-side caches I've been are unable (because they are so
generic) to map the dependency between a page and its images. So for
example, maybe the page gets a hit, which keeps it in the cache but the
i
I would look at OSCache. Or, if you're using something like Hibernate,
you can just set the expritations on your catalog objects to a very
long time. That will still render every time, but at least you won't
be going to the database.
On 7/14/05, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> Hi,
>
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 book
10 matches
Mail list logo
