Hello Everybody
We are searching for improving the performance for our projects which use
Tapestry.
We have done a lot of work to optimise the performance on all the layers:
1. db layer
2. object-relational mapping layer, we use ehcache to keep the result
of any query between requests
3. even
I hope I'm not violating an NDA when I say that SeeSaw, the big UK
video-on-demand Tapestry project, went down this path. They eventually
turned off a huge amount of the features that, to me, make Tapestry
special, including all dynamically generated JavaScript ... mostly to
support more aggressive
Hi, one of my simple implementation, hope it helps.
public abstract class StaticCacheComponent {
private final static int CACHE_EXPIRED = 60;
@Inject
private ComponentResources componentResources;
@Inject
private CacheService cacheService;
@Inject
private TypeCoerc
Hi Magnus,
many thanks for the detailed cookbook. I will give it a try and let you
know and have a nice holiday.
Jens
Am 30.07.12 00:03, schrieb Bård Magnus Kvalheim:
Hi Jens,
As it happens I too was thinking about this a while back.
I didn't make any research, but I would probably look i
Hi Jens,
As it happens I too was thinking about this a while back.
I didn't make any research, but I would probably look into making mixin or
component using the before and after render phases.
Saving/caching the markup in after - and then short-circuit in before if
cache is valid. I think is sho
Hi Christian!
Many thanks for your answer. Unfortunately, rendering is the expensive
part, as we already rely on cached data.
Jens
Am 28.07.12 13:49, schrieb Christian Riedel:
Hi,
I think theres no easy way to intercept the rendered result of a single
component (that contains a lot of ot
Hi,
I think theres no easy way to intercept the rendered result of a single
component (that contains a lot of other components). But you could put this
component inside some kind of dummy-page, asynchronously call its url from an
internal caching-service and store the output using simple I/O st
Hi T5'ers
we have some performance issues and started thinking about caching our
pages (lets say parts of them to be precise). Due to the fact we are
showing user related information along with "public information" on a
page, we can not make use of a simple web proxy caching.
Therefore we ar
