Cache

[daliborjanak]

Tileserver could be faster when it could be possible to create cache files of metadata. Idea:

1. create variable in globalconfig 'cache' with values true or false (default could be false)
2. if global cache is true, tileserver will generate cache files if they are requested:
   a) index.json
   b) layer1json, layer2.json etc.
   c) we can also cache wmts files to file like wmts/1.0.0/WMTSCapabilities.xml
3. Create link for quick working with cache:
   www.server.dom/cache-clean - delete cache
   www.server.dom/cache-create - create cache

With this we can compute more metadata attributes in future.

We can store cache into root directory when tileserver.php is located and serve it via webserver or store it in folder 'cache' and serve it via script (first check if file exists, then return file or create and return).

[klokan]

I don't see the speed of metadata delivery as an issue at this point. Tiles should be for high performance served by webserver directly. Metadata attributes should not be computed but generated, if the tiles are generated in advance as well.

This has very low priority for me personally.

Implementation will bring installation issues (required rights to write from PHP).

Efficient caching should be done on the webserver (mod_cache) level or on CDN cache such as http://www.cloudflare.com/ or http://www.fastly.com/.

The target of this project should be only proper caching HTTP headers on the content which is dynamically generated.

[daliborjanak]

This will bring more problems then benefits. Maybe this ticket shoud be opened in future. Now it's not issue of tileserver.