It depends on when the data is first accessed. If it was first accessed at 0 min then it will refresh when Case 2 accesses. However, if the first access is at 4 min, then the lapse time to 7 min is only 3 min so Case 2 will not refresh.
The countdown starts when the Data Page is first accessed. You can't stop the countdown, not even if you accessed it n times.
After the countdown expires, i.e. the data is stale, the next refresh is upon the next access, so this could be after m min. At the next point of access when data is stale, data is refreshed and countdown begins again. You cannot stop the countdown.
Within this countdown period, data is considered fresh so no data fetch is needed.
So, a clock "resets" only after countdown expires, not when it is accessed. When u access the Data Page, either during the countdown or after it expires, will determine if the data is fetched from the clipboard or from the data source again.
Posted: 6 years ago
Posted: 21 Jun 2015 11:52 EDT
Teng Hao Chua (chuat)
Global Tech Enablement, Senior Instructor
This has become more confusing now. below excerpt from Transcript:
Remember the Reload If Older Than refresh strategy is a countdown for inactivity of a data page. For example, if we set the time to one week we would need one week between the page being accessed before the data becomes stale.
Doesnt it mean, countdown is between last and latest access?
I read in another post that you cleared the CSA exam. Congratulations!!
As to how the Reload if Older Than refresh strategy works, it is very much a typical TTL (Time to Live) cache behavior. The refresh interval is based on when the data page was loaded and has nothing to do with when it was last accessed.
As an example, lets consider Reload if older than is set to be 10 min.
1. Data page is accessed for 1st time at 1200, it is loaded as this is first access
2. Data page is accessed for 2nd time at 1208, it is not reloaded, existing copy is returned
3. Data page is accessed for 3nd time at 1211, it is reloaded as the time from last reload has exceeded provided 10 min.
What you are reading is a bug in the documentation - and I will follow up to make sure it is corrected ASAP.