[mapserver-dev] Tile Access API

[Paul Ramsey]

I think being able to turn off access modes via a map file
configuration is GOOD.
I think having them turned off by default is BAD.
Ease of use, ease of set-up. Most people don't need the protection of
having services off by default, and will struggle to figure out the
magic word to let them in. Having the services off by default degrades
the "Mapserver experience" for that very large proportion of people
who don't need the protection.  For those rare cases of people who do
set up a service and suddenly find themselves overwhelmed with
traffic, we provide the "easy out" of a flag to turn the services off.
The only exception to the above is WFS, since GIS people have an
irrational proprietary instinct towards their vector data, so I would
argue that WFS GetFeature should be off by default.

P

On Wed, Apr 16, 2008 at 7:13 AM, Kralidis,Tom [Burlington]
<Tom.Kralidis at ec.gc.ca> wrote:
>
>  You could, but many times this is not set (i.e. I don't set this and let
>  MapServer derive the URL value -- more portable).
>
>
>  ..Tom
>
>
>  > -----Original Message-----
>  > From: mapserver-dev-bounces at lists.osgeo.org
>  > [mailto:mapserver-dev-bounces at lists.osgeo.org] On Behalf Of
>
> > bartvde at osgis.nl
>  > Sent: 16 April, 2008 9:58 AM
>  > To: Steve Lime
>  > Cc: mapserver-dev at lists.osgeo.org
>  > Subject: Re: [mapserver-dev] Tile Access API
>  >
>
>
> > Why not checking if
>  > ows_onlineresource/wms_onlineresource/wfs_onlineresource etc.
>  > have been set?
>  >
>  > On Wed, 16 Apr 2008 08:40:36 -0500, "Steve Lime"
>  > <Steve.Lime at dnr.state.mn.us> wrote:
>  > > 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
>  > >
>  >
>  > _______________________________________________
>  > mapserver-dev mailing list
>  > mapserver-dev at lists.osgeo.org
>  > http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>  >
>  _______________________________________________
>  mapserver-dev mailing list
>  mapserver-dev at lists.osgeo.org
>  http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>