[Qgis-developer] QEP: QGIS Mapserver Python Plugins

[aperi2007]

Another question could be the timeout.

Infact. If a processing take too much time to end.
It should go in timeout.
So not only concurrency need, but also a timeout system to avoid the 
lock never ending of resources.

A.

Il 30/08/2014 13:21, Alessandro Pasotti ha scritto:
> 2014-08-29 18:05 GMT+02:00 René-Luc Dhont <rldhont at gmail.com>:
>> Le 29/08/2014 16:54, Alessandro Pasotti a écrit :
>>
>>> 2014-08-29 16:39 GMT+02:00 René-Luc Dhont <rldhont at gmail.com>:
>>>> Hi Alessandro
>>>>
>>>> Thanks for this interesting input.
>>>> I'm happy to test it and to develope some use case.
>>>> I thought it's a good feature and can help to enhance QGIS-Server easily
>>>> :
>>>> WPS, WMTS, Table Join Service, WFS2 or other that OGC does not already
>>>> know.
>>>>
>>>> Regards,
>>>> René-Luc
>>>>
>>>>
>>> Hello René-Luc,
>>>
>>> I'm happy to hear that you are going to test it, please let me know how it
>>> goes!
>>>
>>> Keep in mind that it's just a proof of concept, and yes, we need a RFC
>>> or QEP: the current implementation is the simplest, less obtrusive and
>>> quickest that I could think about.
>>>
>>> For example, I would consider adding real signals attached to plugins
>>> slots and cached parsed projects passed to plugin instances...
>>>
>>> I'm currently working on a WPS server plugin that bridges Processing
>>> and PyWPS (version 3.2.2 since the latest version 4 is tightly bound
>>> to werkzeug), now fighting with parameters but it basically works.
>>
>> Can I help ?
>>
>> I already done some works on it !
>>
>>>
>>> Regards
>>
> Hello,
>
> I've got a first highly experimental Processing-PyWPS bridging plugin:
> https://github.com/elpaso/qgis-wps
>
> * I've only tested grass convex hull with a small shapefile
> * GetCapabilties and other requests work with GET calls ony
> * it needs Processing patches otherwise it hangs when reading pipes
> from shell process (see [1])
> * Processing needs other patches as well to support concurrent
> requests (for example the grass temporary script storage should be
> done in tempfile instead of the current processing folder)
>
> I don't know Processing enough to say if there aren't any other big
> showstoppers for this plugin.
>
> Still a lot of work to do :)
>
>
>   [1] https://github.com/elpaso/QGIS/commit/afbfb7f12b8f62731d40745035d919532ae5da1f
>