-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The asset caching mechanism should update assets based on HTTP headers #6
Comments
Before we discussed about this case, I wrote this in the cache manager
It's probably awful and works for image only. I'll change this code and work with your option! |
For above example, it's not fully functional as it doesn't dereference/rereference the asset. |
It has several flaws actually. First, it assumes that assets are images, this is not true as it can be videos too. Regarding #12, this piece of code will be executed each time the I implemented this inside the client |
First part was a first inspiration and can be cancelled. |
Currently, the caching mechanism is not updating assets in cache at any time. It should use the information exposed in HTTP headers (Last-Modified, Cache-Control, etc) to update assets in cache.
We have to define a policy for this update mechanism to trigger. Sending an HTTP request every time the
PluginManager
sees a slide referencing an external asset seems a bit heavy, but it is the policy that ensures the most consistent cache.The text was updated successfully, but these errors were encountered: