Discussions
Categories
Choose a Product
THRUST SERVICES
CORE APPS
CE PRODUCTS
...
Quick Links
POPULAR
HELPFUL TIPS
Groups
My Links
FOR SIGNED IN MEMBERS:
Back to website
Home
TeamSite
TeamSite, LiveSite and OpenDeploy
custom component cache keys
Migrateduser
Hi
We need to cache components based on some user attributes which are not segments and not passed into a component (so does not impact the component checksum). What is the best approach to caching these components ?
I've got 3 possible solutions but I'm not happy with the first and I don't know how to implment the other two :-)
Option 1 - add each attribute as a site segment and execute each segment on every page. (segments are used in the component cache key) this has the draw back of performance (executing the segments for each page render) which we have over came a little with custom segment execution code. however it also has the draw back of creating an un-wanted site map for our users to get confused by. (is there a way of having a site segment without a site map ?)
option 2 - create a custom implementation of the component cache pool which allows custom cache keys to be used. or maybe we don't have to do this and we can config existing cache pool ?. This is the solution i'm most interested in as it seems the correct approach in our situation
option 3 - hack the user attributes into the component defintion and pass in the values at run time so that the component checksum uses these values to be calculated. The checksum is used as part of the cache key. I suppose a bit like ls_page_name being available to use in the component defintion. Again what is the best way to expose the user attributes in this way ?
Open to other options
Cheers Lee C
Find more posts tagged with
Comments
There are no comments yet