Cert++
Close

Local versus remote includes for cached and personalized fragments

Key Takeaway

A local include is cached only as part of the page around it. Use a remote include (<isinclude url="">) for any fragment that needs a different cache time or must not be cached.

An ISML template can pull other content into a page in two ways. A local include brings in another template. A remote include brings in the output of a separate request. The difference matters for caching. A local include is cached only as part of the page around it. A remote include can have its own caching or none, so one page can mix cached content with personalized content.

The page cache and the iscache tag

B2C Commerce stores HTML pages generated from ISML templates in the page cache, but only when the template contains the <iscache> tag. An example of the tag is <iscache type="relative" hour="24">. The tag can sit anywhere in the template.

The <iscache> tag is ignored when the page caching preference isn't enabled in Business Manager. For Storefront Reference Architecture (SFRA) implementations, configure caching with middleware.

B2C Commerce Developer Study Guide

Checklist progress

0/237Learned

Given a development task, code ISML templates that use functionality, such as local include, remote include, components, and other ISML tags

0/14

Prepare for the Exam

Play Today's Certle

Study Community

Ask questions and get the latest info from other B2C Commerce Developer studiers. 796 members and growing.