Difference between revisions of "Cache Lifetime"
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
==Where to find it== | ==Where to find it== | ||
| − | * ''Manager'' > '''Administration > [[Server Settings]]''' menu > '' | + | * ''Manager'' > '''Administration > [[Server Settings]]''' menu > '''General''' page > ''Caches and Timeouts'' category > '''{{PAGENAME}}''' |
==Purpose== | ==Purpose== | ||
| − | SAP Enable | + | SAP Enable Now content objects that are displayed in the browser (typically for Learner playback) will be cached in the browser. If a user displays the same object within the number of seconds specified in this setting, the cached version will be (re)displayed. If more than this number of seconds has elapsed, a new version will be retrieved from SAP Enable Now. |
==Use== | ==Use== | ||
Latest revision as of 07:33, 28 November 2023
Where to find it
- Manager > Administration > Server Settings menu > General page > Caches and Timeouts category > Cache Lifetime
Purpose
SAP Enable Now content objects that are displayed in the browser (typically for Learner playback) will be cached in the browser. If a user displays the same object within the number of seconds specified in this setting, the cached version will be (re)displayed. If more than this number of seconds has elapsed, a new version will be retrieved from SAP Enable Now.
Use
Using a high(er) value here will reduce network traffic, but could conceivably impact users' ability to see the 'latest' version of an object. However, if the content is not rapidly changing, you can probably set this relatively high (a day would not be unreasonable in a steady-state scenario).
Setting Cache Lifetime to -1 will prevent the content from being cached at all, and a new copy will be retrieved every time the user displays it.
