Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
14 Cards in this Set
- Front
- Back
|
What does REST stand for? |
Representational state transfer |
|
|
What are the six principles of RESTful APIs? |
1. Client-server 2. Stateless 3. Cacheable 4. Uniform interface 5. Layered system 6. Code on demand (optional) |
|
|
What does client-server entail? |
UI and data storage are separated. Increases UI portability and server scalability. |
|
|
What does statelessness entail? |
Requests from clients must contain all info to fulfill a request. No stored context. |
|
|
How does cacheability work? |
Response headers flag cacheability. If true, clients are given the right to reuse data later. |
|
|
What are the constraints of a uniform interface? |
- Identification of resources - Manipulation of resources - Self-descriptive messages - Hypermedia as the engine of application state |
|
|
Describe a layered system |
Component logic is is as separate as possible to increase performance and scalability |
|
|
What is code on demand? Example? |
The allowance of distribution or API by direct download. e.g. distribution through a package manager |
|
|
What is a resource? |
Anything which can be named |
|
|
What is a resource identifier? |
How a resource is discovered. Usually a URI. (URL == subset of URI) |
|
|
How are resources represented? |
- Timestamp - Data (results) - Metadata - Extra Hypermedia links |
|
|
What is media type? |
The data format of the representation. e.g. application/json |
|
|
What are web resource methods? |
HTTP methods of GET, PUT, POST, DELETE |
|
|
How should query based API results be represented? |
By links, not identifiers |
