rest/json: Difference between revisions
Jump to navigation
Jump to search
(resources) |
|||
| Line 18: | Line 18: | ||
# allows paging and/or partial returns of large datasets | # allows paging and/or partial returns of large datasets | ||
# standardizes linking to related resources | # standardizes linking to related resources | ||
# use of hypermedia (links + context) to manage application state | # use of hypermedia (links + context) to manage application state | ||
# does NOT become a full-fledged RPC solution | # does NOT become a full-fledged [http://hideoustriumph.wordpress.com/2008/05/05/ws-deathstar-for-the-rest-of-us/ RPC] solution | ||
== Resources == | == Resources == | ||
Revision as of 16:21, 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