[WFS] Set max features to 0

[Paul Ramsey]

Perhaps... the intent is to have access to DescribeFeatureType (in  
order to compose valid SLD) while not allowing GetFeatures to return  
any features (to protect the actual feature sources).  All hail the  
WMS/SLD combination, neutered without partial WFS access!

P

On 15-Feb-06, at 8:55 PM, Steve Lime wrote:

> Clint: Perhaps I don't understand the question, but doesn't setting  
> DUMP FALSE for a given layer get you this? That should keep WMS  
> GetFeature and any WFS request from returning feature information,  
> yet allow maps to be made.
>
> Steve
>
>>>> Clint Johnson <cjohnson at REFRACTIONS.NET> 02/15/06 7:00 PM >>>
> Hi guys,
>
> Is it possible to disable a layer's contents from appearing in a
> GetFeature WFS request in terms of a mapping file setting?  If not,  
> then
> can you give any advice reguaring where I can add such functionality
> into the mapserver source code?
>
> I essentially want to have a mechanism where I "protect my data"; that
> is, where a complete graphical representation of my data (aka map) can
> be viewed via a GetMap WMS request, yet be private/encapsulated by  
> means
> of hidden to WFS request (in terms of not returning any features for a
> WFS request).  And selective in the sense that this functionality  
> can be
> applied on a per layer basis without having to completely disable WFS
> altogether.
>
> I've looked at the mapserver source code (all occurrences of
> MAXFEATURES/maxfeatures) and I see a lot of checks for >0 -- which
> reaffirms my observation that "MAXFEATURES 0" is the same as not
> specifying MAXFEATURES at all.  My guess is that anything less than 1
> (and by default -1) is being used denote MAXFEATURES as being not set.
>
> Thanks,
> Clint