[Pywps-dev] REST interface

[Jachym Cepicky]

As Tom and Jorge write. See also geoserver REST API for inspiration
http://docs.geoserver.org/stable/en/user/rest/api/

po 15. 6. 2015 v 9:09 odesílatel Jonas Eberle <jonas.eberle at gmx.de> napsal:

> I like this example very much. Such an approach was also used by istSOS -
> a Python framework for Sensor Observation Services. Any administration of
> this service is available based on such a REST API, see this link for a
> description:
> https://geoservice.ist.supsi.ch/projects/istsos/index.php/IstSOS_WAlib_2.0
>
> Cheers,
> Jonas
>
>
> ----- Am 14. Jun 2015 um 22:21 schrieb Tom Kralidis <tomkralidis at gmail.com
> >:
>
> Thanks for the info - sounds great! Are you implementing WPS REST based on
> an OGC profile or best practice?
>
> Having said this, it might be valuable to investigate the degree of
> RESTful-ness one can achieve (i.e. using pure HTTP verbs instead, etc.).
> For example:
>
> http://example.org/wps # capabilities
> # config (needs auth)
> http://example.org/wps/server/config
> http://example.org/wps/server/instances
> http://example.org/wps/server/processes
>
> And so on.
>
> Sent from my iPhone
>
> > On Jun 14, 2015, at 15:55, Calin Ciociu <calin.ciociu at gmail.com> wrote:
> >
> > Hello everyone,
> >
> > As some may know I am working during the summer for Google Summer of
> Code 2015.
> > My job is to implement a REST interface for PyWPS-4.
> >
> > So REST won't be much different than the actual way a client makes
> requests.
> > Something along the lines of "
> http://localhost:5000/wps?SERVICE=wps&OPERATION=GetCapabilities"
> >
> > What I was thinking was to add additional operation for different tasks
> like for example get the server configuration or the list of running server
> instances and processes. Also be able to set some configuration, control
> processes etc. (Which might require also some kind of security otherwise
> anyone can just go ahead and stop or deploy servers/processes)
> >
> > What do you guys think?
> > Does this sound like a plan or should I have something different like "
> http://localhost:5000/rest?operation=foo&..."?
> >
> > Best regards,
> > Calin Ciociu
> > _______________________________________________
> > pywps-dev mailing list
> > pywps-dev at lists.osgeo.org
> > http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev
> _______________________________________________
> pywps-dev mailing list
> pywps-dev at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev
>
> _______________________________________________
> pywps-dev mailing list
> pywps-dev at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pywps-dev/attachments/20150616/d3ef2e91/attachment.html>