Skip to content
This repository has been archived by the owner on May 3, 2022. It is now read-only.

redesign namespace extensions #15

Open
sgratzl opened this issue Dec 21, 2016 · 4 comments
Open

redesign namespace extensions #15

sgratzl opened this issue Dec 21, 2016 · 4 comments
Labels
type: feature New feature or request

Comments

@sgratzl
Copy link
Contributor

sgratzl commented Dec 21, 2016

In the current version, plugins can register namespace extensions that are essentially flask/wsgi applications. The question is whether instead of using annotations and objects that are fixed we use a plain annotation or declaration (swagger) approach.

see also connextion

In the current version, the plugins don't include flask directly anymore but 'phovea_server.ns' that rexports flask at the moment.

features needed similar to flask

  • rest api functions
  • access to parameters (request.args, request.values)
  • form files access
  • specify response type
  • generator as response for streaming (either asynchronous definition or event-stream)
  • websocket definition
@sgratzl
Copy link
Contributor Author

sgratzl commented Dec 23, 2016

django main request/response objects: https://docs.djangoproject.com/en/1.10/ref/request-response/

@sgratzl
Copy link
Contributor Author

sgratzl commented Dec 29, 2016

@sgratzl
Copy link
Contributor Author

sgratzl commented Dec 29, 2016

see also https://github.com/zalando/connexion

@sgratzl
Copy link
Contributor Author

sgratzl commented Jan 1, 2017

first test under the feature_swagger branch. dataset, idtype, and last_deployment apis are changed. So, you can access: http://localhost:9000/api/dataset/ui/

@rumersdorfer rumersdorfer added type: feature New feature or request and removed Layer: API labels Nov 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants