+1 on the idea, i actually ran into this problem recently and this would
have been quite useful. So I guess this means all the capabilities
transformers will have to be updated as well... which at this point is quite
a few. And what does "hidden" mean when it comes to the other requests...
GetFeature, GetMap, etc... should the services check the hidden flag when
those resources are accessed individually?
The idea I had before was to try and use a thread local catalog approach to
this, similar to how the virtual services hide layers not in the local
workspace. Basically an filter/callback/etc... would set up a thread local
view of the catalog (with a custom resource access manager, etc...) that
would prevent access to hidden layers. The benefit of this approach being
that no service code would really have to be updated at all.
$0.02
-Justin
On Tue, Sep 6, 2011 at 1:22 AM, Andrea Aime <[email protected]>wrote:
> Hi,
> I'd like to propose (and implement) a new feature for the GeoServer
> configuration,
> the ability to hide a layer from the capabilities: simple checkbox
> making the layer
> available, or not.
>
> A hidden layer can be useful in some cases:
> - the layer should be part of a group, but we want to show the group,
> not the inner
> layers, to the world
> - the layer is temporary and somehow linked to a user session, we don't
> want
> to show it to the wide world yet we need it to be around and usable from
> OGC service calls
> - the layer is going to stay there, but it's a service one, something that
> a
> particular application uses under covers but that we don't want normal
> clients
> to see and use (not for security issues, but just to avoid
> making the capabilities contents too verbose/confusing)
>
> The idea would be to add the flag to LayerInfo, as a new method in the API.
> Yet I'd need to have this in 2.1.x too (this would be a sponsored feature),
> and we have had a number of these issue in the past... I think I have
> a solution:
> - on 2.1.x add the property in the interface, but make it a derived one
> picking
> on the user map
> - on trunk add the field as a Boolean, and inspect the user map as a
> fallback
> when the field is not set
>
> Opinions?
>
> Cheers
> Andrea
>
> --
> -------------------------------------------------------
> Ing. Andrea Aime
> GeoSolutions S.A.S.
> Tech lead
>
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
>
> phone: +39 0584 962313
> fax: +39 0584 962313
>
> http://www.geo-solutions.it
> http://geo-solutions.blogspot.com/
> http://www.youtube.com/user/GeoSolutionsIT
> http://www.linkedin.com/in/andreaaime
> http://twitter.com/geowolf
>
> -------------------------------------------------------
>
>
> ------------------------------------------------------------------------------
> Special Offer -- Download ArcSight Logger for FREE!
> Finally, a world-class log management solution at an even better
> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
> download Logger. Secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsisghtdev2dev
> _______________________________________________
> Geoserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
