Opened 15 years ago
Last modified 15 years ago
#1332 new defect
Tile Cache should only be cleared if the saved Map Definition resource has changes in base layer — at Initial Version
Reported by: | jng | Owned by: | |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | Tile Service | Version: | |
Severity: | critical | Keywords: | |
Cc: | External ID: |
Description
The Tile Cache invalidation logic should be more refined. Currently saving a Map Definition will invalidate the tile cache for that layer, even if there were no changes to the base layer settings.
The Tile Cache should only be invalidated when there are changes found in the base layer section of the Map Definition. For example, adding dynamic layers to a Map Definition with tiled layers and saving that resource should not clear the tile cache as the tiles are still valid.
Steps to reproduce:
- View any web layout containing a map definition w/ tiled layers
- A generated folder containing the tiles should be in the defined TileCache folder
- Perform any change to this map definition that does not affect the base layers (eg. Changing the description, adding an untiled layer, etc) and save it.
- That generated folder is now deleted. Nothing was changed in the base layer settings so this folder (and all generated tiles within) should have remained.
Note:
See TracTickets
for help on using tickets.