Diferencia entre revisiones de «Usuario:Lmorillas/desarrollo web servidor/django/rest»
De WikiEducator
(Página creada con '{{MiTitulo|REST con Django}} == Qué es REST == * http://en.wikipedia.org/wiki/Representational_State_Transfer') |
|||
| Línea 3: | Línea 3: | ||
== Qué es REST == | == Qué es REST == | ||
* http://en.wikipedia.org/wiki/Representational_State_Transfer | * http://en.wikipedia.org/wiki/Representational_State_Transfer | ||
| + | |||
| + | == Características == | ||
| + | ; Client-Server | ||
| + | : There should be a separation between the server that offers a service, and the client that consumes it. | ||
| + | ; Stateless | ||
| + | : Each request from a client must contain all the information required by the server to carry out the request. In other words, the server cannot store information provided by the client in one request and use it in another request. | ||
| + | ; Cacheable | ||
| + | : The server must indicate to the client if requests can be cached or not. | ||
| + | ; Layered System | ||
| + | : Communication between a client and a server should be standardized in such a way that allows intermediaries to respond to requests instead of the end server, without the client having to do anything different. | ||
| + | ; Uniform Interface | ||
| + | : The method of communication between a client and a server must be uniform. | ||
| + | ; Code on demand | ||
| + | : Servers can provide executable code or scripts for clients to execute in their context. This constraint is the only one that is optional. | ||
Revisión de 20:36 18 dic 2013
Qué es REST
Características
- Client-Server
- There should be a separation between the server that offers a service, and the client that consumes it.
- Stateless
- Each request from a client must contain all the information required by the server to carry out the request. In other words, the server cannot store information provided by the client in one request and use it in another request.
- Cacheable
- The server must indicate to the client if requests can be cached or not.
- Layered System
- Communication between a client and a server should be standardized in such a way that allows intermediaries to respond to requests instead of the end server, without the client having to do anything different.
- Uniform Interface
- The method of communication between a client and a server must be uniform.
- Code on demand
- Servers can provide executable code or scripts for clients to execute in their context. This constraint is the only one that is optional.
