Uniform interface hierarchic resource identification Verbs to perform operations manipulation through representation HATEOAS
Richardson maturity model hierarchic resource identification Verbs to perform operations manipulation through representation HATEOAS Really well explained by Fowler: http://martinfowler. com/articles/richardsonMaturityModel.html#level0
Richardson maturity model mess hierarchic resource identification Verbs to perform operations HATEOAS
Richardson maturity model 0. mess hierarchic resource identification Verbs to perform operations HATEOAS
The web is not meant for invalidating data.Server should not be able to keep clients state, otherwise they wont scale well.Thats why long-polling and endless connections havent had big success dealing with caching.
HTTPs cache fails when dealing with really dynamic pages,because consumers will always have to hit the origin server,although a part of the page would be cacheable ( header and footer, for example )
ESI was built for that http://www.w3.org/TR/esi-lang
Edge Side Includes A de facto standard for bla bla bla...
Edge Side Includes A de facto standard for bla bla bla... Server side includes ( not SSI! ) usually handled by the architectures ESI processor. http://www.w3.org/TR/esi-lang http://www.w3.org/TR/edge-arch
Like it or not, XML is a friend of the non BC-breaking evolutionhttp://www.slideshare.net/Wombert/xml-versus-the-new-kids-on-the-block-phpbnl11-20110129 http://www.odino.org/320/long-live-xml-too-sorry-for-json-fanboyz
"REST is software design on the scale of decades: every detail is intended to promote software longevity and independent evolution. Many of the constraints are directlyopposed to short-term efficiency. Unfortunately, people are fairly good at short-term design, and usually awful at long-term design. " Roy Fielding