easysoa/EasySOA — Issue #96: Improve Content Automation to support the EasySOA API
Author: mkalam-alami
Created: 2012-01-18 15:44:01+00:00
State: open
Labels: Nuxeo, Open Wide

## Planning

1. Define precisely the EasySOA API needs
2. Evaluate if the Content Automation (CA) is appropriate
3. Make the changes to the CA and implement the EasySOA API on top of it

## CA vs EasySOA API

### Opportunities

* Allows to leverage the numerous existing Nuxeo web services
* Eases the use of OAuth?

### Issues/required evolutions

Allow for more [RESTful services](http://en.wikipedia.org/wiki/Representational_state_transfer#RESTful_web_services)*, by exposing an alternative version of CA**:

* That works by directly passing the parameters (no wrapping into a "params" field, no "context" and "input" used for chaining)
* That allows better use of the HTTP methods (GET/POST/PUT/DELETE)
* That is resource oriented

*Among the benefits of this, we can also mention a better integration with an eventual Backbone.js-powered UI.
**Via a proxy?