rest/json: Difference between revisions
Jump to navigation
Jump to search
(CouchDB) |
(resources) |
||
| Line 22: | Line 22: | ||
== Resources == | == Resources == | ||
* [http://bitworking.org/news/restful_json Original proposal] | * [http://bitworking.org/news/restful_json Original proposal] by Joe Gregorio | ||
* [http://www.json.com/2008/08/19/standardizing-restful-json/ Standardizing RESTful JSON] by Kris Zyp | |||
* [http://groups.google.com/group/restful-json Google Group] | * [http://groups.google.com/group/restful-json Google Group] | ||
* [AtomPub] (for comparison/inspiration) | * [http://tools.ietf.org/html/rfc5023 AtomPub] (for comparison/inspiration) | ||
== Proposals == | == Proposals == | ||
Revision as of 16:15, 4 September 2008
RESTful JSON
Charter
Given that:
- REST is a powerful architecture for scalable web services
- JSON is a lightweight container for exchanging data
- AtomPub, while RESTful, requires XML documents with strict metadata requirements
The goal of the RESTful JSON project is to develop a series of conventions for:
- URLs
- HTTP methods
- HTTP headers
- JSON fields
that:
- is maximally compatible with existing (RESTful, generic) clients
- enables partial updates
- allows paging and/or partial returns of large datasets
- standardizes linking to related resources
- use of hypermedia (links + context) to manage application state
- does NOT become a full-fledged RPC solution
Resources
- Original proposal by Joe Gregorio
- Standardizing RESTful JSON by Kris Zyp
- Google Group
- AtomPub (for comparison/inspiration)
Proposals
Implementations
- CouchDB
- Jester (same URLs as ActiveResource)
- Dojo REST store
- DOM Resource
- Persevere
- SproutCore