[OpenLayers-Users] [OT] TileCache, server-side WMS-C implementation

[percy]

Chris, could you summaraze the main difference in between using this and 
using ka-map? Is it mainly easier to configure? What do you think the 
performance trade-offs are?

How does this fit in with the osgeo tiling specification?
http://wiki.osgeo.org/index.php/WMS_Tile_Caching

Thanks,
Percy

Christopher Schmidt wrote:
> A couple people asked about this earlier on the mailing list, so I
> thought I'd post here, and let everyone know that TileCache, the 
> MetaCarta Labs BSD licensed WMS-C server implementation, is now
> available from http://labs.metacarta.com/wms-c/#TileCache .
> 
> """
> TileCache is a Python-based WMS/TMS server, which supports pluggable
> caching mechanisms and rendering backends. At its simplest, it requires
> only write access to a disk, the ability to run Python CGI scripts, and
> a WMS you want to be cached. With that, you can create your own local
> disk-based cache of any WMS server, and use the result in any WMS-C
> supporting client, like OpenLayers, or any TMS supporting client, like
> OpenLayers and worldKit.
> 
> When running under mod_python, TileCache can handle hundreds of cache
> requests per second.
> """
> 
> Download: http://labs.metacarta.com/wms-c/tilecache-1.0.tar.gz
> Browse Source: http://labs.metacarta.com/wms-c/tilecache-1.0.tar.gz/
> Demo: http://labs.metacarta.com/wms-c/demo.html
> 
> OpenLayers is, by default, a client for TileCache, and an
> OpenLayers-based demonstration of the tilecache server is included in
> the download.  
> 
> Regards,

-- 
David Percy
Geospatial Data Manager
Geology Department
Portland State University
http://gisgeek.pdx.edu
503-725-3373