[OWSLib-devel] Force async/sync in WPS execute
k204199
ehbrecht at dkrz.de
Wed Apr 25 08:21:46 PDT 2018
Hi Adam,
I have merged now all my outstanding patches into the master of OWSLib for the wps module including the async option.
There is another issue now because “async” will be a reserved keyword starting with Python 3.7. Maybe you have a good alternative name for it, see ticket:
https://github.com/geopython/OWSLib/issues/455 <https://github.com/geopython/OWSLib/issues/455>
Cheers,
Carsten
> On 28. Jan 2018, at 21:51, Adam Laža <ad.laza32 at gmail.com> wrote:
>
>
>
> 2018-01-22 13:46 GMT+01:00 Carsten Ehbrecht <ehbrecht at dkrz.de <mailto:ehbrecht at dkrz.de>>:
> Hello,
>
> I also would like to have the async/sync switch. I have done this on my fork already:
>
> https://github.com/bird-house/OWSLib/blob/1887376ead09e04c60af2bc615414715c62a3611/owslib/wps.py#L274 <https://github.com/bird-house/OWSLib/blob/1887376ead09e04c60af2bc615414715c62a3611/owslib/wps.py#L274>
>
> It is using a simple async boolean parameter … easier to understand. Choose what ever you find more appropriate.
>
> Oh, thanks for the lineage parameter I forgot it in my solution.
> I agree that a simple async parameter is easier to understand. I suppose an use-case when client requests to store status but not to update it, is not very probable.
>
>
> Would be nice to get this into the OWSLib library.
>
> +1
>
>
> Cheers,
> Carsten
> --
> Carsten Ehbrecht
> Abteilung Datenmanagement
>
> Deutsches Klimarechenzentrum GmbH (DKRZ)
> Bundesstraße 45 a • D-20146 Hamburg • Germany
>
> Phone: +49 40 460094-148 <tel:%2B49%2040%20460094-148>
> FAX: +49 40 460094-270 <tel:%2B49%2040%20460094-270>
> Email: ehbrecht at dkrz.de <mailto:ehbrecht at dkrz.de>
> URL: www.dkrz.de <http://www.dkrz.de/>
>
> Geschäftsführer: Prof. Dr. Thomas Ludwig
> Sitz der Gesellschaft: Hamburg
> Amtsgericht Hamburg HRB 39784
>
> > On 22. Jan 2018, at 06:25, Jachym Cepicky <jachym.cepicky at gmail.com <mailto:jachym.cepicky at gmail.com>> wrote:
> >
> > Hi,
> >
> > the change seems reasonable, I think, it's worth the pull request
> >
> > J
> >
> > ne 21. 1. 2018 v 22:01 odesílatel Adam Laža <ad.laza32 at gmail.com <mailto:ad.laza32 at gmail.com>> napsal:
> > Hi devs,
> >
> > currently I am working on an extension to PyWPS project using OWSLib. I need to send an execute request to a server but in sync mode. However in code [1] attributes 'status' and 'storeExecute', which - at least in case of PyWPS - determine the async/synchronity - are hardcoded to true.
> >
> > For my needs I added parameters to WPSExecution.execute() and buildRequest() methods [2]. I'm just wondering if 'status' and 'storeExecute' parameters are hardcoded for any reason? If not, is it desired functionality and my approach to force async/sync mode right?
> >
> > Thanks in advance.
> > Adam
> >
> > [1] https://github.com/geopython/OWSLib/blob/master/owslib/wps.py#L613 <https://github.com/geopython/OWSLib/blob/master/owslib/wps.py#L613>
> > [2] https://github.com/lazaa32/OWSLib/commit/bb94b710c83b48e9f179d29a51f61dffec00475a <https://github.com/lazaa32/OWSLib/commit/bb94b710c83b48e9f179d29a51f61dffec00475a>
> > _______________________________________________
> > OWSLib-devel mailing list
> > OWSLib-devel at lists.osgeo.org <mailto:OWSLib-devel at lists.osgeo.org>
> > https://lists.osgeo.org/mailman/listinfo/owslib-devel <https://lists.osgeo.org/mailman/listinfo/owslib-devel>
> > _______________________________________________
> > OWSLib-devel mailing list
> > OWSLib-devel at lists.osgeo.org <mailto:OWSLib-devel at lists.osgeo.org>
> > https://lists.osgeo.org/mailman/listinfo/owslib-devel <https://lists.osgeo.org/mailman/listinfo/owslib-devel>
>
>
> _______________________________________________
> OWSLib-devel mailing list
> OWSLib-devel at lists.osgeo.org <mailto:OWSLib-devel at lists.osgeo.org>
> https://lists.osgeo.org/mailman/listinfo/owslib-devel <https://lists.osgeo.org/mailman/listinfo/owslib-devel>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/owslib-devel/attachments/20180425/533f3cea/attachment.html>
More information about the OWSLib-devel
mailing list