RESTful / Hypermedia backend
Created by: bignaux
I'm trying to add RESTful/hypermedia capabilities to paperwork to use it for example -
- give a try to http://ckan.org as storage . Using such dataset software could be a real alternative to bloated DMS/CMIS solution.
- angularjs UI (mobile ready and other thing)
- documented API without need of language binding...
I've studied a lot of architecture pattern on the subject. I began with a Flask based solution. They are a lot of thing in frontend that need to be moved in backend (perharps job scheduling).
Advantages
• far better data model ( settings:ocr/devices , document ) • asynchronous (for non blocking) • multiclient connection (thanks http) • authentication (thank http) • validation ( json schema on the go) • versionnable API • less code • easier to develop backend/frontend see https://en.wikipedia.org/wiki/HATEOAS • plugin pattern using http://lv2plug.in/ns/ but json-ld instead of rdf for plugin description/discovery see hydra over restful here http://www.markus-lanthaler.com/hydra/spec/latest/core/