How does the Mid-tier's "Definition Change Check Interval" work?

Product

Midtier 7.

Midtier 7.0.1
Environment
Reference
In the Mid-tier cache, the last time a definition change was made (meaning a Form, active link etc) is
maintained. When the time lapse set in "Definition Change Check Interval" completes, the Mid-tier queries
(upon next access) the active AR server, comparing the last time the element was retrieved (Mid-tier) againt the
last time that definition was changed (AR Server).
If something that was previously cached over Midtier has changed on the AR server, then the entire cache for
that specific AR server is flushed, and the requested definitions are retrieved again from the AR Server.
If nothing was modified on the AR server then Midtier waits for the next time lapse to finish and rechecks.
The information logged by midtier when a change is detected is the following
FINE (com.remedy.log.PERFORMANCE) : (Thread 16) com.remedy.arsys.share.Cache$ServerReaper$1 run
webteam02 Cache Change Times: 1215534302 1211497575 1215632904
FINE (com.remedy.log.PERFORMANCE) : (Thread 16) com.remedy.arsys.share.Cache$ServerReaper$1 run
webteam02 Last Record Times: 1215534302 1211497575 1215632827
WARNING (com.remedy.log.CACHE) : (Thread 16) com.remedy.arsys.share.Cache$ServerReaper$1 run
Detected definition change on server webteam02 - old time was 1215632827 new time is 1215632904
WARNING (com.remedy.log.PERFORMANCE) : (Thread 16) com.remedy.arsys.share.Cache$ServerReaper$1
run Detected definition change on server webteam02 - old time was 1215632827 new time is
1215632904