Hi,
I have been successfully using the CacheControlMarkupRenderer from the
ioko-tapestry-commons
http://tapestry.formos.com/projects/ioko-tapestry-commons/ library.
This is a java class that implements the MarkupRendererFilter and
Partial MarkupRendererFilter in order to apply caching headers
and the
MarkupRendererFilter
Hello
From my point of view this kind of caching mechanism should be done in
front
of your application server.
Regards
Christophe.
2009/10/15 Ian Petzer ian.pet...@ioko.com
Hi,
I have been successfully using the CacheControlMarkupRenderer from the
ioko-tapestry-commons
http
To: Tapestry users
Subject: Re: Lifecycle of a tapestry request and the
MarkupRendererFilter
What not using the prepareResponse of the StreamResponse Tapestry
interface
to set headers ?
2009/10/15 Ian Petzer ian.pet...@ioko.com
Hi,
We do actually have a load balanced caching system sitting in front
.
This is a more servlet-style of development, which may be the right
approach for a transitional application.
On Thu, Oct 23, 2008 at 8:33 AM, Ian Petzer [EMAIL PROTECTED] wrote:
Hi,
We are busy converting our Struts/Tiles based application to Tapestry.
Until
this is complete I have am
Hi,
We are busy converting our Struts/Tiles based application to Tapestry. Until
this is complete I have am required to generate links to the new Tapestry
pages correctly from the jsp pages.
Normally this isn't a problem as I used the url pattern of:
HOST/PAGE/PARAM1/PARAM2/PARAM3
Now, please
