[mapserver-dev] Tile Access API

[Kralidis,Tom [Burlington]]

> -----Original Message-----
> From: mapserver-dev-bounces at lists.osgeo.org 
> [mailto:mapserver-dev-bounces at lists.osgeo.org] On Behalf Of 
> Daniel Morissette
> Sent: 16 April, 2008 8:32 AM
> To: mapserver-dev at lists.osgeo.org
> Subject: Re: [mapserver-dev] Tile Access API
> 
> 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?
> 

This wouldn't be a bad idea.  I've seen numerous instances where people
unknowingly stood up a MapServer CGI and suddenly a WMS endpoint is
born, so:

1./ The WMS has no metadata, and / or is not configured for WMS
2./ Unintended bandwidth.

..Tom


> 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
>