Tile Caches hvor man dynamisk opdaterer tiles hvor der er sket opdatering af data bør alle dage være en bedre udnyttelse af ressourcerne og giver samtidig slutbrugeren den bedste performancemæssige oplevelse ... Prisen er mindre fleksibilitet i forhold til lag kontrol ...
/Sik
Tile Caches plus dynamic generation of map tiles due to data updates is by far the best resource usage scheme and at the same time the best performance experience for the end user ... The price is less flexibility when it comes to the layer control ...
/Sik
Quote
Written by Richard Marsden
[...] TileCache attempts to solve this problem by providing a cache between the WMS map server and the client. It has two methods of operation. The first renders the tile using either MapServer or Mapnick as a rendering back end. The third method can cache WMS tiles fetched from a remote WMS service.
TileCache supports client requests in the form of WMS, WorldWind, or TMS.
TileCache also supports two different cache mechanisms. The DiskCache mechanism stores cached tiles as image files. The MemoryCache mechanism stores data in a memcached instance or cluster. Memory storage is even faster than disk storage, but this not appropriate for a shared web server, or a web server with limited memory. Memcached is a distributed memory object caching system developed by Danga Interactive to enhance the popular LiveJournal.Com site. Information and downloads for memcached can be found here.
TileCache is distributed under the BSD license. It requires Python to be installed on the host server. Further information, downloads, and installation instructions can be found on the TileCache website. A good TileCache Tutorial can be found at the GeoServer.org site. [...]
Read more: http://www.geowebguru.com/articles/152-wms-tile-caches
Ingen kommentarer:
Send en kommentar