(해석 또는 이해가 잘못된 부분이 있다면 댓글로 편하게 알려주세요.)
That’s it for our quick introduction to HTTP. In this chapter, we highlighted HTTP’s role as a multimedia transport protocol. We outlined how HTTP uses URIs to name multimedia resources on remote servers, we sketched how HTTP request and response messages are used to manipulate multimedia resources on remote servers, and we finished by surveying a few of the web applications that use HTTP.
-> 지금까지 HTTP에 대해 빠르게 소개해 보았습니다. 이번 챕터에서는 멀티미디어 전송 프로토콜로써 HTTP가 맡은 역할을 조명했습니다.
-> 우리는 HTTP가 원격 서버의 멀티미디어 리소스를 명명하기 위해 어떻게 URI를 사용하는지, HTTP 요청과 응답 메시지가 이 리소스들을 조작하기 위해 어떻게 사용되는지 간단히 알아보았습니다.
-> 그리고 이 챕터는 HTTP를 사용하는 몇 가지 웹 애플리케이션을 정리하며 마무리되었습니다.
The remaining chapters explain the technical machinery of the HTTP protocol, applications, and resources in much more detail.
-> 남은 챕터에서는 훨씬 더 구체적으로 HTTP 프로토콜과 애플리케이션, 리소스에 대한 기술적인 장치들을 설명합니다.
Later chapters of this book will explore HTTP in much more detail, but you might find that some of the following sources contain useful background about particular topics we covered in this chapter.
-> 이후 챕터들은 더 상세하게 HTTP를 탐색하겠지만, 다음의 몇 가지 소스들은 이번 챕터에서 다룬 특정 주제들에 대한 유용한 배경지식이 포함되어 있을 수 있습니다.
HTTP Pocket Reference (Clinton Wong, O’Reilly & Associates, Inc.)
This little book provides a concise introduction to HTTP and a quick reference to each of the headers and status codes that compose HTTP transactions.
This W3C web page contains many great links about the HTTP protocol.
http://www.ietf.org/rfc/rfc2616.txt
RFC 2616, “Hypertext Transfer Protocol—HTTP/1.1,” is the official specification for HTTP/1.1, the current version of the HTTP protocol. The specification is a well-written, well-organized, detailed reference for HTTP, but it isn’t ideal for readers who want to learn the underlying concepts and motivations of HTTP or the differences between theory and practice. We hope that this book fills in the underlying concepts, so you can make better use of the specification.
http://www.ietf.org/rfc/rfc1945.txt
RFC 1945, “Hypertext Transfer Protocol—HTTP/1.0,” is an informational RFC that describes the modern foundation for HTTP. It details the officially sanctioned and “best-practice” behavior of web applications at the time the specification was written. It also contains some useful descriptions about behavior that is deprecated in HTTP/1.1 but still widely implemented by legacy applications.
http://www.w3.org/Protocols/HTTP/AsImplemented.html
This web page contains a description of the 1991 HTTP/0.9 protocol, which implements only GET requests and has no content typing.
http://www.w3.org/Protocols/WhyHTTP.html
This brief web page from 1991, from the author of HTTP, highlights some of the original, minimalist goals of HTTP.
http://www.w3.org/History.html
“A Little History of the World Wide Web” gives a short but interesting perspective on some of the early goals and foundations of the World Wide Web and HTTP.
http://www.w3.org/DesignIssues/Architecture.html
“Web Architecture from 50,000 Feet” paints a broad, ambitious view of the World Wide Web and the design principles that affect HTTP and related web technologies.
The World Wide Web Consortium (W3C) is the technology steering team for the Web. The W3C develops interoperable technologies (specifications, guidelines, software, and tools) for the evolving Web. The W3C site is a treasure trove of introductory and detailed documentation about web technologies.
http://www.ietf.org/rfc/rfc2396.txt
RFC 2396, “Uniform Resource Identifiers (URI): Generic Syntax,” is the detailed reference for URIs and URLs.
http://www.ietf.org/rfc/rfc2141.txt
RFC 2141, “URN Syntax,” is a 1997 specification describing URN syntax.
http://www.ietf.org/rfc/rfc2046.txt
RFC 2046, “MIME Part 2: Media Types,” is the second in a suite of five Internet specifications defining the Multipurpose Internet Mail Extensions standard for multimedia content management.
http://www.wrec.org/Drafts/draft-ietf-wrec-taxonomy-06.txt
This Internet draft, “Internet Web Replication and Caching Taxonomy,” specifies standard terminology for web architectural components.
이 페이지는 Chapter 1을 마무리하는 파트라 그냥 건너뛸까 고민했지만, 마무리를 제대로 하지 않으면 찝찝할 것 같았다. 적어도 나에게는 이 책의 어느 한 페이지도 버릴 부분이 없다. 버리기 아깝다. 혹시나 좋은 정보가 더 남아있지 않을까 하는 생각에 다른 페이지처럼 똑같이 한 줄 한 줄 꼼꼼히 읽었다.
그리고 실제로 p21 ~ p22에서는 HTTP : The Definitive Guide와 함께 읽어보면 좋을 유용한 도서나 웹 페이지들을 많이 추천해주었다. 책을 읽다가 혹은 코딩을 하다가 잘 이해가 되지 않는 부분이 있다면 정리해놓은 페이지를 참고하면 좋을 듯하다.