If there's not too much information to be stored, you could cache the
result of your queries using one of tapestry's persitence mechanisms [1]
or in an ASO [2] and only re-execute your queries when the data has
changed.
Uli
[1]
http://tapestry.apache.org/tapestry5/tapestry-core/guide/persist.html
Hi, i got some ideas.
you can cache the index page as a static html page.
then use the static html page to response to the client.
you can extend tapestry to generate a static html page, just write the index
to a real html file.
then rewrite the client request, the apache httpd docs may help.
2008
Hi,
Nope, you'll have to work something out yourself, as nothing like this
is built into Tapestry.
-Filip
孟凡振 skrev:
Hi all,
I encounter a problem , in my index page a lots of query happens
each time when i reload the it.
so my question here is that is there some cache strategy to ca
Hi all,
I encounter a problem , in my index page a lots of query happens
each time when i reload the it.
so my question here is that is there some cache strategy to cache my index
page?
thanks in advance!!
