I'm not sure I see how that would work. Being that the page is composited before it's delivered, how could an external cache possibly work, or help for that matter? (*Chris*)
On Thu, Oct 21, 2010 at 10:35 AM, Mck <[email protected]> wrote: > On Wed, 2010-10-20 at 15:42 +0200, GF wrote: > > I wish to have something like > > > > <tiles:useAttribute name="header" cacheSeconds="3600" /> > > > > In this way the header "HTML" will be cached for 1 hour. > > I'm looking into integrating tiles with the ESI caching protocol, > particularly the esi:inline protocol (also using its "url" attribute as > used in oracle's implementation). > > This won't provide any internal caching as you suggest. But would allow > an external web accelerator to fragment cache your pages, where your > fragments corresponded with your tiles attributes. To accelerate your > application you would then make it possible for the web accelerator to > fetch just those fragments typically stale by making the application > able to serve individual tiles attributes... > > This is still in the investigation stage, but i'll post any updates. > > ~mck > > >
