iHomeServerâ„¢ maintains its own internal cache database of files that it has indexed via Watch Folders. This database allows iHomeServer to track the created date, last modified date and byte size of each indexable file within your Watch Folders.
When iHomeServer performs a scan of your Watch Folders, it compares the current created date, last modified date and byte size of each file with the value in the database. If either of these properties has changed, the file becomes eligible for reindexing as iHomeServer assumes that the file has been updating.
The cache should maintain itself - for example, when you force an index of a file or folder, you actually tell iHomeServer to remove the relevant records from its cache database; a scan is then initiated and iHomeServer will re-add all the files as if they hadn't been added before. There may some circumstances where the cache gets out of sync, therefore a function is provided that clears the entire cache.
Important Note
When you clear the iHomeServer cache, iHomeServer clears its history of which files it has indexed and which it has not. This means that the next time a scan is triggered (either due to a file change, or due to a schedule), iHomeServer will attempt to re-index all files that are within the database!
:
Count of cached files
Shows the number of files that are currently within the iHomeServer database.
|
|
Clear button
Clears the cache. Note that when you clear the iHomeServer cache, iHomeServer clears its history of which files it has indexed and which it has not. This means that the next time a scan is triggered (either due to a file change, or due to a schedule), iHomeServer will attempt to re-index all files that are within the database!
|
|