Add a json backend into Phoenix

bird-house / pyramid-phoenix

Phoenix is a Pyramid web-application to make it easy to interact with WPS services

http://pyramid-phoenix.readthedocs.io/en/latest/

Apache License 2.0

7 stars 10 forks source link

Add a json backend into Phoenix #138

Closed dbyrns closed 7 years ago

dbyrns commented 7 years ago

We modify some of the phoenix routes to allow a json return format so that an external front-end (https://github.com/Ouranosinc/PAVICS-frontend) can use some of the Phoenix functionalities. Feel free to accept these modifications or to suggest a better approach.

cehbrecht commented 7 years ago

@dbyrns Thanks for the contribution :)

Some comments:

for testing it might be easier to have something like /monitor.json to get the json response.
it's on my todo list to move the job monitoring to the twitcher (which would use json): https://github.com/bird-house/twitcher/issues/21
PyWPS might use json in addition for WPS service communication in the future ... 52 north has already something like this implemented ... in the meantime we could also move this part to the twitcher.
tests would be nice to see we don't break the interface ...

dbyrns commented 7 years ago

I tried to avoid as much as possible any modification to the existing interface but I understand the needs to a .json route. It could be added in the future along with some tests. We will follow with interests the evolution of twitcher since it could fulfill our requirements for a json API. Thank you.

tomLandry commented 7 years ago

It is my understanding that we could rewire the backend to the platform relatively easily. This contribution might not be the "best" solution, but it seemed like the easiest incremental development to hook up our user interfaces. Note that 52North WPS was selected by several OGC participants. Agree for testing. We will test and use Twitcher very soon.