Two big advantages...
- TileCache will do the "metarendering" trick now, which allows you
to render features with labels and edge artefacts cleanly in a tile set.
- TileCache speaks multiple languages in the front and back, which
makes it easier to bind together different services into one tile-
caching system.
Squid would probably outperform TileCache, but you have to bear in
mind that the performance difference is small while the convenience
factor of TileCache is high.
TileCache is what *I* am recommending to people these days. The only
strange thing is how long it took something like TileCache to come
along.
P
On 5-Dec-06, at 10:47 AM, Reid Priedhorsky wrote:
Christopher Schmidt wrote:
In order to improve the scalability of Open Source mapping on the
Web,
MetaCarta Labs has developed a tool we call TileCache. TileCache
acts as
a buffer between your WMS server and its clients. It accepts WMS
requests constrained by scale and bounding box (i.e., WMS-C, as
described by the OSGeo WMS Tiling Client Recommendation[1]), and
returns
images that can be viewed in clients such as OpenLayers.
TileCache also
supports the OSGeo Tile Map Service Specification[2], and requests
in the
format supported by the WorldWind 3D globe client.
Chris,
Very interesting! We need a tool to do this.
We had previously planned on using a generic HTTP caching proxy
server such as Squid. I would be curious to read your take on the
advantages and disadvantages of choosing your tool over something
like Squid.
Thanks,
Reid
_______________________________________________
Geowanking mailing list
[email protected]
http://lists.burri.to/mailman/listinfo/geowanking
_______________________________________________
Geowanking mailing list
[email protected]
http://lists.burri.to/mailman/listinfo/geowanking
