[Pywps-dev] [GSOC] Week report - Web-based administration and process control
Jachym Cepicky
jachym.cepicky at gmail.com
Sat Jun 18 14:44:27 PDT 2016
It makes sense, what Jonas is suggesting - I have no strong opinion about
this, so leave the decision up to you (and support proposal of Jonas)
what about the sqlite issue?
@all: we fased the IOError which pointed to the sqlite driver. If I
understand that correctly, sqlite will always have problems with paralel
writing/reading. @Jan, could you have maybe a look (once you might have
some time) to django, how they are dealing with this issue?
@all: I would suggest to make PostgreSQL another (more robust and safe)
option
j
st 15. 6. 2016 v 13:46 odesÃlatel Jan Rudolf <rudolja1 at fit.cvut.cz> napsal:
> Hello,
>
> yes, these URL's were proposed during our meeting with Jachym. It looks
> better with /processes/*/* ...it's easy to change it, so I will leave it
> for your choice.
>
> Info: I finished yesterday my final exams, so I will focus on GSoC now
> and compensate Monday and yesterday during the weekend.
>
> Jan
>
> On 2016-06-12 23:29, Jonas Eberle wrote:
> > Hi Jan,
> >
> > in your report you wrote:
> > "New API: /, /manage (future web-based administration), /wps (original
> > PyWPS functionality), /pause/process_id (request to pause running
> > process), /resume/process_id (request to resume paused process),
> > /stop/process_id (request to kill process)."
> >
> > I would propose an other structure for the REST-based API:
> >
> > /processes/<process_id>/pause
> > /processes/<process_id>/resume
> > /processes/<process_id>/stop
> >
> > With this we would have a hierarchical structure. You could also have
> > /processes to list (current and past) processes.
> >
> > Jachym, what do you think?
> >
> > Cheers,
> > Jonas
> >
> > ----- Am 12. Jun 2016 um 22:25 schrieb Jan Rudolf
> > <rudolja1 at fit.cvut.cz>:
> >
> >> Hello,
> >>
> >> there is my week report
> >> http://gsoc-2016.jan-rudolf.cz/article/third-week-report
> >>
> >> Cheers, Jan
> >> _______________________________________________
> >> pywps-dev mailing list
> >> pywps-dev at lists.osgeo.org
> >> http://lists.osgeo.org/mailman/listinfo/pywps-dev
> > _______________________________________________
> > pywps-dev mailing list
> > pywps-dev at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/pywps-dev
> _______________________________________________
> pywps-dev mailing list
> pywps-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/pywps-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pywps-dev/attachments/20160618/d52bfa02/attachment.html>
More information about the pywps-dev
mailing list