Again sounds good. A few general comments.
On Fri, Oct 28, 2011 at 3:02 PM, Andrea Aime
<[email protected]>wrote:
> Hi,
> another thing I'll probably be working on in the next weeks is providing
> some level of process filtering and control, in a pluggable way.
>
> A process filter will be an interface allowing to exclude processes from
> the WPS server, it basically will make a process available, or not,
> based on some internal rules.
>
> There are a couple of usages for this kind of filtering:
> - admin control: we ship with a lot of processes, but an administrator
> might want to limit its installation to 2-3 processes only.
> For this case I envision a little GUI panel listing all of the processes
> by
> "namespace" and allowing people to exclude processes and namespaces,
> which would then be stored as a configuration in wps.xml
> - security: some processes might be available only to specific users
> (no implementation planned along this lines, but this will make it
> possible)
>
> I wonder if it would make sense to add processes as another catalog
resource, allowing the admin or whomever to manage them like other resources
in the catalog. It would also fit nicely into the current catalog security
model.
> Another thing that I would like to add is a concept of execution callback,
> similar to the dispatcher callback.
> Such callbacks would be invoked at various stages of a process execution:
> - right after parsing the request
> - right before execution begins, when inputs have been parsed into their
> java equivalent
> - right before the encoding of outputs happens
> - when we are done
>
> The callbacks could do a number of services, for example:
> - security, disallowing certain combinations of processes and inputs
> (e.g., one might want to disallow downloading data from remote hosts)
> - accounting, register who made what wps call, for how long, with how
> much data
>
I like it. The idea of ows service specific callbacks is one I have thought
of before as well. Might be nice to lay down a general pattern for such
callbacks... perhaps giving callback methods for each service operation, and
then some additional ones specific to a operation. Just thinking out loud.
>
> Opinions? Suggestions?
>
> 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
>
> -------------------------------------------------------
>
>
> ------------------------------------------------------------------------------
> The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Cisco Self-Assessment and learn
> about Cisco certifications, training, and career opportunities.
> http://p.sf.net/sfu/cisco-dev2dev
> _______________________________________________
> 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.
------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
