rest/json: Difference between revisions
Jump to navigation
Jump to search
(→Implementations: http://sitepen.com/labs/persevere.php) |
|||
| Line 37: | Line 37: | ||
* [http://www.sitepen.com/blog/2008/06/13/restful-json-dojo-data/ Dojo REST store] | * [http://www.sitepen.com/blog/2008/06/13/restful-json-dojo-data/ Dojo REST store] | ||
* [http://code.google.com/p/dom-resource/ DOM Resource] | * [http://code.google.com/p/dom-resource/ DOM Resource] | ||
* [http://sitepen.com/labs/persevere.php Persevere] | |||
* [http://github.com/sproutit/sproutcore/wikis/sproutcore-rest-api-the-definitive-guide SproutCore] | * [http://github.com/sproutit/sproutcore/wikis/sproutcore-rest-api-the-definitive-guide SproutCore] | ||
Revision as of 00:23, 4 September 2008
RESTful JSON
Charter
[Initial Draft by Dr. Ernie 12:55, 2 Sep 2008 (PDT)]
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
- Google Group
- [AtomPub] (for comparison/inspiration)