ACM Home Page
Please provide us with feedback. Feedback
Principled design of the modern Web architecture
Full text PdfPdf (217 KB)
Source International Conference on Software Engineering archive
Proceedings of the 22nd international conference on Software engineering table of contents
Limerick, Ireland
Pages: 407 - 416  
Year of Publication: 2000
ISBN:1-58113-206-9
Authors
Roy T. Fielding  Information and Computer Science, University of California, Irvine, Irvine, CA
Richard N. Taylor  Information and Computer Science, University of California, Irvine, Irvine, CA
Sponsors
IEEE-CS : Computer Society
SIGSOFT: ACM Special Interest Group on Software Engineering
Irish Comp Soc : Irish Computer Society
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 19,   Downloads (12 Months): 184,   Citation Count: 11
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/337180.337228
What is a DOI?

ABSTRACT

The World Wide Web has succeeded in large part because its software architecture has been designed to meet the needs of an Internet-scale distributed hypermedia system. The modern Web architecture 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. In this paper, we introduce the Representational State Transfer (REST) architectural style, developed as an abstract model of the Web architecture to guide our redesign and definition of the Hypertext Transfer Protocol and Uniform Resource Identifiers. We describe the software engineering principles guiding REST and the interaction constraints chosen to retain those principles, contrasting them to the constraints of other architectural styles. We then compare the abstract model to the currently deployed Web architecture in order to elicit mismatches between the existing protocols and the applications they are intended to support.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
 
2
Anklesaria, F., et al. The Internet Gopher protocol (a distributed document search and retrieval protocol). Internet RFC 1436, Mar. 1993.
 
3
 
4
 
5
Berners-Lee, T., R.T. Fielding, and H.F. Nielsen. Hypertext Transfer Protocol - HTTP/1.0. Internet RFC 1945, May 1996.
 
6
Berners-Lee, T., R.T. Fielding, and L. Masinter. Uniform Resource Identifiers (URI): Generic syntax. Internet RFC 2396, Aug. 1998.
7
 
8
Davis, F., et. al. WAIS interface protocol prototype functional specification (v.1.5). Thinking Machines Corporation, Apr. 1990.
 
9
 
10
Fielding, R.T., J. Gettys, J.C. Mogul, H.F. Nielsen, L. Masinter, P. Leach, and T. Berners-Lee. Hypertext Transfer Protocol -HTTP/1.1. Internet RFC 2616,June 1999. {Obsoletes RFC 2068, Jan. 1997.}
11
 
12
 
13
Garlan, D., and M. Shaw. An introduction to software architecture. Ambriola & Tortola (eds.), Advances in Software Engineering & Knowledge Engineering, vol. II, World Scientific Pub Co., 1993, pp. 1-39.
14
 
15
Kristol, D., and L. Montulli. HTTP State Management Mechanism. Internet RFC 2109, Feb. 1997.
 
16
17
 
18
Postel, J. Media type registration procedure. Internet RFC 1590, Nov. 1996.
 
19
Postel, J., and J. Reynolds. File Transfer Protocol. Internet STD 9, RFC 959, Oct. 1985.
20
 
21
Sollins, K., and L. Masinter. Functional requirements for Uniform Resource Names. Internet RFC 1737,Dec. 1994.
 
22

CITED BY  11

Collaborative Colleagues:
Roy T. Fielding: colleagues
Richard N. Taylor: colleagues