On Mon, Jul 18, 2011 at 8:55 AM, <[email protected]> wrote:
> Hello Justin, thank you for yours answers!
>
> > No list unfortunately. And since processes are pluggable, and
> > how their parameters are parsed are pluggable I think it
> > would be hard to come up with an exhaustive list. Perhaps
> > trying to sum up all the ppio implementations.
> >
>
> Ok. I just noted that providing list or dictionaries to the wps script as
> input causes the geoserver wps query builder to display a complex input
> method...so i wondered how you could trigger a compley input field in
> general...
>
> > Regarding rasters... I have never written a process that
> > takes a raster, so not sure what that looks like. There
> > should be lots of examples though. There is no support (yet)
> > in geoscript for rasters so it would be just the straight
> > java class, grid coverage, or grid coverage reader, etc...
> > that would be the parameter type. If I understand correctly.
> >
> >
> > > 3) Is it planned to implement process specific access
> > control mechanism, comparable to the data specific security
> > rules? I don't want to generally allow users to use WPS, but
> > I also would like to fine-tune access based on certain
> > services or namespaces!
> >
> >
> > At the moment there is no such a thing. There are
> > people expressing
> > interest like you,
> > but until there is sponsoring to implement it during
> > working hours I
> > doubt it will happen
> >
>
> In general I understand that you don't have more time than you have...it is
> for me the same ;-) ...I just wonder what priority processing has for
> Geoserver in the future? I remember reading that Geoserver should become the
> GEO platform fo the web, also making it easy to deploy services by it. So is
> this WPS/Python just an experimental playground (and maybe removed again any
> time) or is a confortable API within Geoservers roadmap?
>
> This is really important for me/my institution, because we're currently in
> the middle of making platform decisons!!
Well again it is tough to say. WPS is definitely becoming more popular and
thanks to the tireless efforts of Andrea it has actually become usable and
stable. But on an open source project like this one development is driven by
one of two things. 1. Clients funding certain development, or 2. Developers
like Andrea who spend much of their free time on the project. Both of which
the community as a whole doesn't have that much control over. Who knows when
a client will wish to fund a specific feature. And who knows what a
developer will choose to work on during his weekend. I can definitely say
there is interest and a desire to make geoserver WPS into something great
and well supported, but time will tell.
As for the python extension the intention is the same. Although in this case
I hope to see it move to something supported (promoted to extension status)
soon, as I plan to present on it at this years FOSS4G, so want to clean it
up before hand.
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
10 Tips for Better Web Security
Learn 10 ways to better secure your business today. Topics covered include:
Web security, SSL, hacker attacks & Denial of Service (DoS), private keys,
security Microsoft Exchange, secure Instant Messaging, and much more.
http://www.accelacomm.com/jaw/sfnl/114/51426210/
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
