Thank you Andrea for your fast reply! (Further responses in the message body)
> > 1) So far all default WPS services do not support async processing: > > <ProcessDescription wps:processVersion="1.0.0" > statusSupported="false" storeSupported="false"> > > > > Is there general support for async requests by the WPS extension? > > Is there any way to change these properties when setting up > > a process via the Python Scripting? If not, would it be > > possible to implement a hook for status & store procedures in > > the python scripts (E.g. def store() & def status())? > > Asynch support is part of the WPS engine, not of the specific process > (the specific process > should just provide support for injecting a ProgressListener). > Unfortunately not, we don't have such support in the engine, it needs > to be developed. True, it makes sense to support this by the engine and only let the the procresses (e.g. Python script) provide listeners. My idea in short: We will run processes which probably run longer than an open session. My plan therefore is to offer the user a "process web-interface" which shows their schedulded job with current status and if processes finish let them store their results (maps) by registering new layers via the the Geoserver REST API. Any ideas if or how this could be done (today/in future)? Furthermore, are there any plans concerning supporting async processing in the WPS engine or (at least) status support? Is there generally a roadmap for the future of WPS in Geoserver? I remember reading that Geoserver should become a platform for serving not only data but also services. If that the case (And i hope Geoserver is going this direction) than we would also need improved APIs (Java, Python, ...) to implement processes dynamically without rebuilding Geoserver and the WPS extension each time. The Python Scripting is already a good start. > > 2) I saw that I can influence the process' input > > descriptors (and WPS request builder UI) by using different > > types/objects in my python script, for instance basic python > > types (str, int, double, etc.) produce literal input > > descriptors whereas objects imported from geoscript > > (Geometry, Point, Polygon) lead to complex nput descriptors. > > Are there other input types I could use? Is there a list or > > better documentation available? In my case I would like to > > specify rasters as inputs to my service! > > This one I cannot answer, don't use the python module. The maintainer > went away for a two weeks vacation > just yesterday, not sure if someone else will be able to > answer in the meantime. > A pitty. Is it posible to inform him by email on return or contact him directly if he's back? > > 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 > Ok. I find this an important issue, but not the most urgent one! ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
