[Pywps-dev] [GSoC] Pause/Resume/Kill process response - Web-based administration

Jan Rudolf rudolja1 at fit.cvut.cz
Fri Jun 17 06:49:05 PDT 2016


OK, so I am going to implement JSON responses for the new URL API for
now, it's also easier for me. 

What information do you want to see in this response? 

My guess:
1) an identifier
2) time
3) the uuid
4) a message like status: "paused/killed/resumed"

Jan

On 2016-06-17 15:19, Jonas Eberle wrote:
> Hi all, 
> 
> I would recommend not to mix responses based on OGC WPS (equal to
> XML-based responses) with requests that are not in line with "typical"
> WPS requests. 
> 
> I would assume the following: 
> 1) If the request is something like
> /wps?service=WPS&request=Pause&jobid=<process_id> (this is a typical
> WPS request) the response should be XML-based along with or based on
> the XML defined by the WPS specification. 
> 2) If the request is something like /processes/pause/<process_id> (not
> defined at all by OGC) the response, in my opinion, should be
> JSON-based (because this is easier for every programming language!)
> 
> The first is OGC-like, the second is completely different from any OGC
> specification. 
> 
> Furthermore: Is it "good pratice" to include elements, such as
> "wps:ProcessPaused", that are not in line with the XML schema of the
> WPS specification?
> 
> Cheers,
> Jonas
> 
> ----- Am 17. Jun 2016 um 14:50 schrieb Jan Rudolf
> <rudolja1 at fit.cvut.cz>:
> 
>> Hi,
>>
>> I've implemented pause/resume/kill into PyWPS in a form, that you
>> make
>> HTTP request with /processes/pause/<process_id>, the process is
>> paused
>> and you will get just text response "<process_id> is paused". I
>> think,
>> that Jachym said, you want the response in an XML form like:
>>
>> <wps:ExecuteResponse ...>
>> <wps:Process wps:processVersion="None">
>> <ows:Identifier>sleep</ows:Identifier>
>> <ows:Title>Sleep Process</ows:Title>
>> <ows:Abstract>This process will sleep for a given delay or 10
>> seconds if not a valid value</ows:Abstract>
>> </wps:Process>
>> <wps:Status creationTime="2016-06-16T22:13:25Z">
>> <wps:ProcessAccepted>PyWPS Process sleep
>> accepted</wps:ProcessAccepted>
>> </wps:Status>
>> </wps:ExecuteResponse>
>>
>> so for paused/killed/resumed processes is going to be similar
>> response
>> only with different status? <wps:ProcessPaused>PyWPS Process sleep
>> paused</wps:ProcessPaused> for example.
>>
>> Thanks, Jan
>> _______________________________________________
>> pywps-dev mailing list
>> pywps-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/pywps-dev


More information about the pywps-dev mailing list