- Building Microservices with Go
- Nic Jackson
- 369字
- 2021-07-15 17:28:06
URIs
One of the main components in the HTTP protocol is a URI. URI stands for Uniform Resource Identifiers and is the method by which you will access the API. You may be asking what the difference between a URI and a URL (Uniform Resource Locator) is? When I started to write this chapter, I wondered about this myself and did what any self-respecting developer would do, which is to head over to Stack Overflow. Unfortunately, my confusion only grew as there were lots of detailed answers, none of which I found particularly enlightening. Time to head over to the inner circle of hell also known as W3C standards to look up the RFC for the official answer.
In short, there is no difference, a URL is a URI that identifies a resource by its network location, and it is acceptable to interchange the terms when describing a resource entirely.
The clarification document published back in 2001 (http://www.w3.org/TR/uri-clarification) goes on to explain that in the early to mid-90s there was an assumption that an identifier is cast into one or two classes. An identifier might specify the location of a resource (URL) or its name (Uniform Resource Name URN) independent of location. A URI could either be a URL or a URN. Using this example, http:// would be a URL scheme and isbn: a URN scheme. However, this changed over time and the importance of the additional level of hierarchy lessened. The view changed that an individual scheme does not need to be cast into one of a discrete set of types.
The conventional approach is that http: is a URI scheme and urn: is also a URI scheme. URNs take the form urn:isbn:n-nn-nnnnnn-n, isbn: is a URN namespace identifier, not a URN scheme or a URI scheme.
Following this view, the term URL does not refer to a formal partition of URI space rather, URL is an informal concept; a URL is a type of URI that identifies a resource via its network location.
For the rest of this book, we will use the term URI and when we do we will be talking about a method to access a resource that is running on a remote server.
- Java入門(mén)經(jīng)典(第6版)
- Python量化投資指南:基礎(chǔ)、數(shù)據(jù)與實(shí)戰(zhàn)
- Python Deep Learning
- Web開(kāi)發(fā)的貴族:ASP.NET 3.5+SQL Server 2008
- 實(shí)戰(zhàn)低代碼
- Scratch 3.0少兒編程與邏輯思維訓(xùn)練
- Mastering Linux Security and Hardening
- 持續(xù)輕量級(jí)Java EE開(kāi)發(fā):編寫(xiě)可測(cè)試的代碼
- C#開(kāi)發(fā)案例精粹
- Learning Grunt
- Scratch從入門(mén)到精通
- Software-Defined Networking with OpenFlow(Second Edition)
- HTML5與CSS3權(quán)威指南
- 編程的原則:改善代碼質(zhì)量的101個(gè)方法
- 零基礎(chǔ)C語(yǔ)言學(xué)習(xí)筆記