[mapserver-dev] Tile Access API

[Steve Lime]

I think this is a good idea as well, one that we've talked about in the past with regards
to OGC services. Perhaps an explicit MAP-level tag or WEB-level metadata with a 
delimited list of supported services:

  ALLOWED_SERVICES 'WMS,TILES,WFS:1.0;1.1'

Steve

>>> Daniel Morissette <dmorissette at mapgears.com> 04/16/08 7:32 AM >>>
Paul Ramsey wrote:
> 
> The barn door is already wide open on this one, and is already being
> traversed, but clients like ArcExplorer over WMS, Google Earth over
> WMS, and as you note OpenLayers over WMS.  You put up a server, egads,
> people use it!
> 
> A tile API is actually an improvement, since it's at least trivially
> easy to get proxy caching behavior within the constrained URL space
> provided by the tiling system.
> 

You've got good points, but I wonder if we should do something to 
protect our users who are not aware of the risk of their servers getting 
overloaded by those clients and limit the damage by having this feature 
disabled by default. If someone enables it then they need to understand 
the risk and live with it, but at least those who are not prepared to 
deal with that kind of load are not exposed by default.

I guess if we follow this logic we should disable all OGC web service 
interfaces by default as well... maybe we should? What do you all think?

Daniel
-- 
Daniel Morissette
http://www.mapgears.com/
_______________________________________________
mapserver-dev mailing list
mapserver-dev at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-dev