|
TileCacheOp
– a configurable operator, that simply puts its source tiles into a cache.# | Title | User Story | Importance | Notes |
---|---|---|---|---|
1 | Operators own tile-cache | Any tile-computing operator can have its own, configurable tile-cache. Users can configure it through graph XML or the GUI. By default, there is no tile-cache. Disposing operators after execution will definitely empty their tile-caches. | Must have |
|
2 | TileCacheOp | TileCacheOp is a configurable, source tile-pulling operator, that simply puts its source tiles into a cache. It can be used within a graph to force tile-caching at a given point. | Optional | |
3 | No global tile-cache | Remove global tile-caching entirely. |
Include any mockups, diagrams or visual designs relating to these requirements.
Below is a list of questions to be addressed as a result of this requirements document:
Question | Outcome |
---|---|
If there is not a single tile-cache, how is it ensured that tile-caches do not grow too big? By giving each tile-cache it's own capacity? Or is there a central capacity administration? | Communicate the decision reached |