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
The cache can get into a bad state or cached assets can get stale.
Let's remove the tediousness of manually fixing cache files and just have a worker thread or process which periodically refreshes and verifies the cache.
The text was updated successfully, but these errors were encountered:
a different multi-threaded handler? i was thinking about to load whole ".cache_list" to memory as temporary sources (also throw new cache here).. but talking was easy..
I think your idea is similar to what I was thinking. My general idea is to load the .cache_list into memory and do the following:
Purge any cache files which have a timestamp in the original URL, for example, delete any asset where the URL looks like *.granbluefantasy.jp/*?t=*.
For all other files, check with the server if the asset was updated on the Granblue server. If it was updated, download and cache the new version.
So, I think this is the same as what you said. However, the reason to do this in a separate worker thread is implementation and performance. I want to keep the logic for the "cache refresh" separated from the proxy server code, and I also don't want to be refreshing the cache while the proxy is busy.
The cache directory gets quite large so I don't want a cache refresh, which could take a long time, to block the normal proxy operations.
The cache can get into a bad state or cached assets can get stale.
Let's remove the tediousness of manually fixing cache files and just have a worker thread or process which periodically refreshes and verifies the cache.
The text was updated successfully, but these errors were encountered: