REST emphasizes scalability of component interactions, generality of interfaces, independent deployment of components, and intermediary components to reduce interaction latency, enforce security, and encapsulate legacy systems.
REST provides a set of architectural constraints that, when applied as a whole, emphasizes scalability of component interactions, generality of interfaces, independent deployment of components, and intermediary components to reduce interaction latency, enforce security, and encapsulate legacy systems.
Readings:
•Fielding, Roy Thomas. Architectural Styles and the Design of Network-based Software Architectures. Doctoral dissertation, University of California, Irvine, 2000. - http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm
•Principled Design of the Modern Web Architecture by ROY T. FIELDING and RICHARD N. TAYLOR, ACM Transactions on Internet Technology, Vol. 2, No. 2, May 2002, Pages 115–150.
•http://www.infoq.com/articles/rest-introduction
•http://www.infoq.com/articles/designing-restful-http-apps-roth
•http://www.youtube.com/watch?v=YCcAE2SCQ6k
•http://www.ietf.org/rfc/rfc3986.txt
•http://soa.dzone.com/news/rest-%E2%80%93-good-bad-and-ugly
•http://rest.blueoxen.net/cgi-bin/wiki.pl?WhatIsREST#nid652
•http://www.prescod.net/rest/
•http://www.prescod.net/rest/rest_vs_soap_overview/
•http://www.petefreitag.com/item/431.cfm
•http://en.wikipedia.org/wiki/Representational_State_Transfer
•http://www.xfront.com/REST-Web-Services.html
•http://dret.net/netdret/docs/soa-rest-www2009/
•http://rest.elkstein.org/2008/02/what-is-rest.html
1 comments:
REST is labeled as "lightweight" web integration. One aspect of this lightweight compared to web services, is that there is no need for client proxy, which means there no need for complex consumer side programming (in many cases).
Post a Comment