July 2025
Intermediate to advanced
414 pages
11h 21m
Spanish
Content preview from Aprendizaje de estilos de API
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Capítulo 5. REST
Este trabajo se ha traducido utilizando IA. Agradecemos tus opiniones y comentarios: translation-feedback@oreilly.com
Representational State Transfer (REST) es la API basada en red más popular.1 El estilo arquitectónico REST2 fue formulado en 2000 por Roy Fielding en su tesis doctoral "Architectural Styles and the Design of Network-Based Software Architectures", como enfoque para crear aplicaciones basadas en red a escala de Internet.
Este capítulo repasa los orígenes, la implementación, las pruebas, la seguridad, la documentación y las ventajas y desventajas de las API REST. En implementarás una API REST utilizando el marco de trabajo REST de Django (DRF), para el Servicio de Previsión Meteorológica (WFS), presentado en "Servicio de Previsión Meteorológica".
HTTP, recurso y URI
En la práctica de , los objetivos arquitectónicos de REST se traducen en tres componentes principales: HTTP, un recurso y una URI.
HTTP es el vaso sanguíneo de Internet, y la mayoría de los estilos de API descritos en este libro utilizan HTTP para intercambiar mensajes. Lo soportan clientes como navegadores web, herramientas de línea de comandos como curlHTTP es un protocolo de capa de aplicación que puede estar basado en texto o ser binario.3
Puedes encontrar más detalles sobre HTTP en el Capítulo 4.
En REST, cualquier información que pueda nombrarse puede ser un recurso: por ejemplo, un documento, una imagen, un valor numérico de cero o incluso una persona (un ser humano, una entidad ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.