Ben,
we chose a bit of a different approach and added html caching for CQ a
while back
http://www.headwire.com/svn/projects/cqbpcache/trunk/cqbpcache/
basically,we use a tag that allows you to monitor changes in a path and
cache the html accordingly until a node in the path (or one if its
subnodes) changes.
Feel free to try it out, feedback welcome
Ruben
On 7/28/2014 11:15 PM, Ben Zahler wrote:
Hi all,
We are considering to implement a resource-based caching in Sling.
I have found some efforts to do something similar in the past, but they all
seem to have been either abandoned or do something different from what we have
in mind.
So it would be great to get some feedback if it this has been tried before and
was given up or if our idea is just not what the Sling-world is waiting for.
This is what our Sling-Cache would do:
- deliver sling resources from cache based on an exact path
- deliver sling resources from cache for a subtree of the repository
The following scenarios would benefit from such a cache:
- navigation components that are expensive to calculate and are identical
for whole subtrees of a site
- cacheable components on non-caheable pages
- CQ use cases with dispatcher caching invalidate the large sections or
the whole cache. After an invalidation, for a short time all traffic hits
CQ/Sling. With resource based caching, this could be improved, allowing Sling
to scale better.
Of course we would create an open-source implementation of our idea, caching
either in memory or in the repository itself and leave room for other
implementations with external caches.
So is this an idea you would love to see implemented or is it rather something
that you deem unnecessarily complex?
Thanks for any feedback!
Cheers,
Ben Zahler
Inside Solutions AG | Bahnhofplatz 11 | 4410 Liestal | Schweiz
Telefon: +41 61 551 00 40 | Direkt: +41 61 551 00 43
http://www.inside-solutions.ch<http://www.inside-solutions.ch/>
