This wiki was in read-only mode for many years, but can now be edited again. A lot of information will need to be updated.
Image Cache Enhancements: Difference between revisions
Add notes on changes to image caching system |
Remove TODO group, that is what the version planing pages are for |
||
| Line 1: | Line 1: | ||
{{DesignDocument}} | |||
==Overview== | ==Overview== | ||
There are several enhancements we can make to our image caching system. | There are several enhancements we can make to our image caching system. | ||
| Line 17: | Line 19: | ||
Some of these challenges may already have solutions, some may need threading or other time management systems to implement properly. | Some of these challenges may already have solutions, some may need threading or other time management systems to implement properly. | ||
Latest revision as of 08:20, 10 February 2013
|
This page contains the design document for an enhancement or feature. It is a work of collaborative development, and may not represent the final design. If you are not part of the development or design group, please post comments and suggestions on the talk page and not in the middle of the design. |
Overview
There are several enhancements we can make to our image caching system.
Tracker Items
https://sourceforge.net/tracker/index.php?func=detail&aid=3602336&group_id=3248&atid=353248
Image Download Confirm
It would be nice to be able to ask the end user if they wish to add a specific server to the allowed downloads. Children who are running with a locked access file should not be asked. The message should be similar to the message for SSL sites with self signed keys in browsers.
Force Reload
In order for a server to use dynamically generated images it must be able to tell clients to reload the image. This has several challenges.
- The client would have to store a hash for the image (may already be done)
- The client would have to know the URL for every image in order to recheck the hash
- Curl would need to tell us if the hash is different from the one on disk
- Curl would need to download the image in the background and not disrupt network play
- The texture system must be able to reload an individual texture from disk with out affecting the frame rate in a bad way.
Some of these challenges may already have solutions, some may need threading or other time management systems to implement properly.