Hi,
Is html fragment caching in 8.1 at the display view level? i.e. 1 cached html fragment per display view per component ?
thanks, Chinmay
Fragment cache is maintained at region level, not at component level even in OWEM 8.1.
Regards,
Deepak.
From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]Sent: Friday, May 25, 2012 1:19 AMTo: eLink RecipientSubject: Fragement caching in 8.1
Fragement caching in 8.1
Posted bychinmay_khandelwal@newyorklife.com (Khandelwal, Chinmay) On 05-24-2012 15:42
thanks,Chinmay
[To post a comment, use the normal reply function]
Forum:
Discussion Group - Web Experience Management
Content Server:
Knowledge Center
Thanks Deepak. So just to make sure that I understand this correctly, if the user adds several components to an unlocked region, there will be only 1 cached html fragment for the entire region. Is that correct? If yes, then what gets invalidated when component level TTL expires?
Chinmay
Hi Chinmay,
Let me correct myself a bit here. The html fragments are actually maintained at component level and that means that there will be one fragment per component ( per display view ) when multiple components exist in a region.
When a component gets invalidated ( because of editing the component for example ) just the corresponding fragment is flushed ; however, when a clear cache operation is performed, this happens at region level (i.e all the component fragments corresponding to the region get invalidated).
Thanks,
Deepak
From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]Sent: Friday, May 25, 2012 7:46 PMTo: eLink RecipientSubject: RE Fragement caching in 8.1
RE Fragement caching in 8.1
Posted bychinmay_khandelwal@newyorklife.com (Khandelwal, Chinmay) On 05-25-2012 10:05
Topic:
