[mapserver-dev] RFC 67 - Enable/Disable Layers in OGC Web Services

[Lime, Steve D (DNR)]

If dump is no longer used and it's use was limited to the OGC service code then now
would be a great time to remove it. We could leave keyword as being recognized but deprecated
and just do nothing in that case. I'd say pull it from the layer structures then.

I agree, don't touch the template thing. That would broader non-OGC impacts.

Steve

-----Original Message-----
From: mapserver-dev-bounces at lists.osgeo.org [mailto:mapserver-dev-bounces at lists.osgeo.org] On Behalf Of Daniel Morissette
Sent: Friday, April 08, 2011 3:58 PM
To: mapserver-dev at lists.osgeo.org
Subject: Re: [mapserver-dev] RFC 67 - Enable/Disable Layers in OGC Web Services

On 11-03-25 02:02 PM, Alan Boudreault wrote:
> Devs,
>
> Currently, the DUMP keyword has to be set to allow a few OGC requests. ie. WFS
> GetFeatureInfo. Since we implemented a way to Enable/Disable OGC web services,
> what about removing that mandatory setting? At the same time, I would also
> remove the TEMPLATE dependency to see if a layer is queryable or not. I
> suppose that to see if a layer is queryable, we would have to check the
> GetFeature/GetFeatureInfo in the *_enable_request?
>

I'd say we should try to drop the DUMP keyword before the next beta if 
we can and if other devs don't expect a problem with that (maybe write a 
motion and discuss it, like we did for the removal of symbol keywords a 
few days ago). I'm thinking especially Assefa and Steve may have an 
opinion on this.

With respect to the template vs query thing, I don't think we should 
touch it.

Daniel
-- 
Daniel Morissette
http://www.mapgears.com/
Provider of Professional MapServer Support since 2000

_______________________________________________
mapserver-dev mailing list
mapserver-dev at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-dev