The document discusses the design of a new application protocol called Waka, which is intended to address some of the current problems with HTTP while maintaining compatibility with the REST architectural style. Waka would have new request and response semantics to make messages more self-descriptive and efficient. It is in early stages of design and has not yet been implemented or deployed, but is intended to eventually be proposed as an Apache project and submitted to the IETF for standardization.
Streamlining Python Development: A Guide to a Modern Project Setup
waka: A replacement for HTTP with less than 40 chars
1. waka: A replacement for HTTP Roy T. Fielding, Ph.D. Chief Scientist, Day Software Director, The Apache Software Foundation Co-founder, Apache HTTP Server Project Elected member, W3C Technical Architecture Group http://www.apache.org/~fielding/
2.
3.
4. EAI - the hard way 4 applications = 6 integrations 5 applications = 10 integrations 6 applications = 15 integrations app5 app1 app2 app3 app4
![How should we design a new application protocol? ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)