Waka (protocol)
From Wikipedia, the free encyclopedia
 |
This article relies on references to primary sources or sources affiliated with the subject, rather than references from independent authors and third-party publications. Please add citations from reliable sources. (February 2012) |
 |
This article is outdated. Please update this article to reflect recent events or newly available information. (February 2012) |
 |
The topic of this article may not meet Wikipedia's general notability guideline. Please help to establish notability by adding reliable, secondary sources about the topic. If notability cannot be established, the article is likely to be merged, redirected, or deleted. (December 2011) |
Waka is an application protocol intended as "a binary, token-based replacement for HTTP."[1] It is "designed to match the efficiency of the REST architectural style."[2]
Contents |
[edit] History
Waka was conceived by Roy Fielding, known for defining the REST architectural pattern, and described in a 2002 ApacheCon presentation.[2] It is still under development. As of August 2006, waka was "all done in my head, it's not on paper though. ... I'm almost to the point where I can make it an open project."[1]
[edit] Distinctives
Some of waka's features include:[2]
- New request semantics (new methods for monitoring and authoring resources)
- Self-descriptive (explicit type, scope, binding of response to request)
- Allow unsolicited responses
- Uniform syntax regardless of type and direction
- Extensible via URIs
- Client-side macros
The waka protocol is named after a type of Maori canoe.
[edit] See also
[edit] References
[edit] External links
 |
This World Wide Web-related article is a stub. You can help Wikipedia by expanding it. |
