[mapserver-dev] Tile Access API

[Steve Lime]

Sometimes I'd like to be able to disable old versions. I'm thinking of WFS specifically given the issues
with GML2 and GML3. Some application schemas will only want GML3.

Steve

>>> On 4/16/2008 at 8:46 AM, in message
<2DC5CCA14756424BBBEE8B4B2E4A682F036CF22C at ecburexch1.ontario.int.ec.gc.ca>,
"Kralidis,Tom [Burlington]" <Tom.Kralidis at ec.gc.ca> wrote:

> +1 for WEB.METADATA.ALLOWED_SERVICES
> 
>  - comma separated
>  - no version specificity implies all versions, mind you, do we want to
> get this fine grained?  Providers (usually) want to support as many
> versions as possible of an interface standard.
> 
> ..Tom
> 
> 
>> -----Original Message-----
>> From: mapserver-dev-bounces at lists.osgeo.org 
>> [mailto:mapserver-dev-bounces at lists.osgeo.org] On Behalf Of Steve Lime
>> Sent: 16 April, 2008 9:41 AM
>> To: mapserver-dev at lists.osgeo.org; dmorissette at mapgears.com 
>> Subject: Re: [mapserver-dev] Tile Access API
>> 
>> 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 
>> 
>> _______________________________________________
>> 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