nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Questions concerning component caching

System

Hello all,

I have a situation where I have multiple 'biography' DCRs. I would like to have only one index.page file, where the biography component sits. I'm halfway to a solution, which involves using a java pre-controller on any url with the pattern:

mysite.com/biographies/*

So, for instance, the pre-controller would receive a request for

mysite.com/biographies/ron-perlman

and point the component to the corresponding DCR.

My problem is when it comes to caching. If LSDS has cached the ron-perlman page, and I submit an update to that DCR, how do I indicate that the component should recache the new version upon the next request?

I'm in a bit of confusion, as the cogency of my post may indicate. Let me know if I need to clarify anything. Any help will be much appreciated.

Find more posts tagged with

Comments

krishna_kumar

I am just trying to help...

In the UI, we have an option : SitePublisher->Invalidate Runtime Cache. That might clear the existing cache and recache the page again.

Or you can set the component cache time to Until Published.

nipper

Do you have LSCS as well as LSDS ? This sounds like a perfect application for LSCS and then the caching will not matter.

Migrateduser

That was our thought as well, nipper, but we were a little concerned (as we've never used LSCS before) about the potential bottleneck ramifications of relying on LSCS queries for every hit. Is that an efficient way to do things? We have multiple heavily-trafficked, 700+-page sites.

Thanks again for all the help!

Screen Shot 2016-04-14 at 1.55.07 PM.png

nipper

That was our thought as well, nipper, but we were a little concerned (as we've never used LSCS before) about the potential bottleneck ramifications of relying on LSCS queries for every hit. Is that an efficient way to do things? We have multiple heavily-trafficked, 700+-page sites.

Thanks again for all the help!

Understand your performance concerns. FYI www.safeway.com is a very serious LSDS/LSCS site (as well as all of their other brands), heavy traffic and all pages go through LSCS (PM me if you want some details on how/why).

Take a look at the same LSCS code, the press release/index/detail sounds very similar to what you want (I really do not like the JS implementation but it works well)

Bowker

Take a look at the same LSCS code, the press release/index/detail sounds very similar to what you want (I really do not like the JS implementation but it works well)

Nipper, can you elaborate on this? Where can one "take a look at [...] LSCS code?" We're about to start to need LSCS type of functionality and I would love to find some examples.

A while back I posted a solution that utilized LSCS from within an XSL component, but that implies that the component was set to "do not cache". Am I missing something or do components that utilize LSCS can't be cached?

nipper

Nipper, can you elaborate on this? Where can one "take a look at [...] LSCS code?" We're about to start to need LSCS type of functionality and I would love to find some examples.

A while back I posted a solution that utilized LSCS from within an XSL component, but that implies that the component was set to "do not cache". Am I missing something or do components that utilize LSCS can't be cached?

Dan.

For his query I suggest he looks at the lscs-sample code. It is a jquery/JavaScript based page to do press releases. It sounds close so what the original question was.

I know there are some issues with caching nd LSCS. We had to write our own cache utility and reported the issue to support.