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; } } }

Need help to understand components caching

TheYann

Hello,

my env is TS 6.5, LiveSite 2.2.1

I am trying to understand the caching system and the cache time option in the components edition window.
I did not really pay attention to it untill today when I decided to change some of the content that drive the rendering of the component.
My component calls an external java function which reads an xml file and generate the result based on its content. I changed that xml content and these changes did not appear in the preview of the component nor the preview of the page the component is in.
I don't have access to a deployment site quite yet.
I DO NOT do any sort of caching in my java class.

Now my questions are:
- why would there be any caching done on the development side?
- what exactly does "until published" means, does it mean "we'll cache eveything until you submit this file to staging and then we'll never cache it again" or something like that?
- does the cache time apply on the back-end (what I called development side) as well as the front-end ?

Thanks in advance folks :-)

Find more posts tagged with

Comments

tec_iwov

We do not cache component renderings within site publisher preview.

Cache until published means that your component will render once and be cached indefinitely. only when you republish the page or use the invalidate cache from the livesite menu will the component be rerendered.

the cache time is only applicable for runtime only

Frederik

A follow up question...

Imagine a Home.page has one (cached) component X that uses a parameter (e.g. id) passed via URL queryString (thus /mysite/Home.page?id=foo). (The case I have in mind is where X shows a specific DCR, where the DCR path/name is passed in by param 'id'. But it could be anything.)

Is it correct to assume that the Home.page will be cached per value of the parameter? The cache will hold an entry of component X for Home.page?id=foo and another for Home.page?id=bar ?

If so, and If component X is set to cache 1 hour, will that timeout apply to each entry individually? So X for Home.page?id=foo could be cached from 8AM till 9AM and X for Home.page?id=bar from 8.15AM till 9.15AM?

TIA!

tec_iwov

yes there will be a different cache reference for each different parameter. As part of 3.0 you need to have that parameter defined as part of the parameter list of the components external.

ccprofessional

Apologies to revive an old thread.

Has anything in the above discussion changed in LS 3.1 (w/ TS 672)?

In TS 671 we had pretty much given up on page and component caching. We are trying out 672 (and LS 3.1) and noticing that url/page caching is working OK, but not too sure about component caching for dynamic (java externals based) components.

Stokes

Apologies to revive an old thread.

Has anything in the above discussion changed in LS 3.1 (w/ TS 672)?

In TS 671 we had pretty much given up on page and component caching. We are trying out 672 (and LS 3.1) and noticing that url/page caching is working OK, but not too sure about component caching for dynamic (java externals based) components.

Yes, it's working as advertised for me in 3.1/672 components.

Stokes.

Migrateduser

i have checked the caching part and have noticed that each unique URI (parameter based) has a separate entry for the component in cache for the same component.

But is there a way to also invalidate the cache for each unique URI rather than removing the entire cache for the component i.e. for all URIs

Mohit

tec_iwov

no you can currently only invalidate the page as a whole and all it's cache refs.
this includes all component cache entries.