You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Much like we now implemented the Favorites caching, we could do the same for other types of files. This implementation would not only offer speed improvements, it also offers redundancy.
Data illegible for caching could be:
A-Z listing (TTL: 1 hour)
Category listing (TTL: 1 week)
TV guide information (e.g. yesterday, today, tomorrow) (TTL: 1 hour)
Favorites (TTL: 1 hour)
The implementation would work like this:
Before downloading a new listing, check if a recent cache exists
Use the cache if recent (timestamp < TTL)
If cache is too old, attempt to download newer version
a. If download failed, use cache anyway, update timestamp
b. If download succeeded, hash content
If hash is different, save to disk
If hash is same, update timestamp
The troubleshooting settings would have an option to clear the caches.
The text was updated successfully, but these errors were encountered:
Describe the bug
Much like we now implemented the Favorites caching, we could do the same for other types of files. This implementation would not only offer speed improvements, it also offers redundancy.
Data illegible for caching could be:
The implementation would work like this:
a. If download failed, use cache anyway, update timestamp
b. If download succeeded, hash content
The troubleshooting settings would have an option to clear the caches.
The text was updated successfully, but these errors were encountered: