Join Morten Rand-Hendriksen for an in-depth discussion in this video Resource, part of Learning REST APIs.
- [Instructor] Let's dig a little deeper…and look at what is meant by two key terms.…Resource and representation.…We'll start with resource.…The concept of REST was defined by Roy Fielding…in a doctoral dissertation in 2000 called…Architectural Styles and the Design…of Network Based Software Architectures.…In this document, we find a pretty clear description…of what a resource is.…He says, the key abstraction of information…in REST is a resource.…Any information that can be named can be a resource:…a document or image, a temporal service,…like today's weather in Los Angeles,…a collection of other resources,…a non-virtual object like a person, and so on.…
In other words, any concept that might be the target…of an author's hypertext reference, must fit within…the definition of a resource.…A resource is a conceptual mapping to a set of entities,…not the entity that corresponds to the mapping…at any particular point in time.…The key here is that last part.…Conceptual mapping.…Consider our librarian.…When you submit a request to the librarian,…
- What is a REST API?
- Who or what interacts with REST APIs?
- Anatomy of a REST request
- HTTP status messages
- Request/response pairs
- GET, POST, and DELETE
Skill Level Beginner
HTTP Essential Trainingwith Morten Rand-Hendriksen50m 18s Beginner
1. REST API: Representational State Transfer Application Programming Interface
4. Request/Response Pairs
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.