Cargando…

REST, hypermedia, and the semantic gap : why "RMM-level3 REST" is not enough /

"Leonard Richardson's 2008 book "RESTful Web Services" taught us the power of the "Uniform Interface" (GET PUT POST & DELETE). His 2013 book, "RESTful Web APIs" goes one step further and describes how Hypermedia APIs can increase flexibility and reusabilit...

Descripción completa

Detalles Bibliográficos
Clasificación:Libro Electrónico
Otros Autores: Amundsen, Michael (Orador)
Formato: Electrónico Video
Idioma:Inglés
Publicado: [Place of publication not identified] : O'Reilly Media, 2015.
Temas:
Acceso en línea:Texto completo (Requiere registro previo con correo institucional)

MARC

LEADER 00000cgm a2200000Ii 4500
001 OR_ocn919515527
003 OCoLC
005 20231017213018.0
006 m o c
007 cr cna||||||||
007 vz czazuu
008 150901s2015 xx 052 o vleng d
040 |a UMI  |b eng  |e rda  |e pn  |c UMI  |d OCLCF  |d UAB  |d OCLCO 
035 |a (OCoLC)919515527 
037 |a CL0500000636  |b Safari Books Online 
050 4 |a QA76.754 
049 |a UAMI 
100 1 |a Amundsen, Michael,  |e speaker. 
245 1 0 |a REST, hypermedia, and the semantic gap :  |b why "RMM-level3 REST" is not enough /  |c with Mike Amundsen. 
246 3 |a Representation state transfer, hypermedia, and the semantic gap 
264 1 |a [Place of publication not identified] :  |b O'Reilly Media,  |c 2015. 
300 |a 1 online resource (1 streaming video file (51 min., 2 sec.)) :  |b digital, sound, color. 
336 |a two-dimensional moving image  |b tdi  |2 rdacontent 
337 |a computer  |b c  |2 rdamedia 
338 |a online resource  |b cr  |2 rdacarrier 
500 |a Title from title screen (Safari, viewed August 25, 2015). 
500 |a Date of publication taken from resource description page. 
511 0 |a Presenter, Mike Amundsen. 
520 |a "Leonard Richardson's 2008 book "RESTful Web Services" taught us the power of the "Uniform Interface" (GET PUT POST & DELETE). His 2013 book, "RESTful Web APIs" goes one step further and describes how Hypermedia APIs can increase flexibility and reusability of APIs. But what are Hypermedia APIs? What do they look like? And why are they "better" than the common CRUD APIs we all use today? This webcast illustrates the differences between CRUD and Hypermedia APIs and how you can design & implement clients and services that can take advantages of APIs based on hypermedia, not just resources and a tiny handful of verbs. Along the way, we'll look at working versions of both styles and get a chance to see why adding more hypermedia in service responses can result in more functionality on the client while reducing the amount of API-specific code on the client."--Resource description page. 
590 |a O'Reilly  |b O'Reilly Online Learning: Academic/Public Library Edition 
650 0 |a Software architecture. 
650 0 |a Representational State Transfer (Software architecture) 
650 0 |a Hypertext systems. 
650 0 |a Application program interfaces (Computer software) 
650 6 |a Architecture logicielle. 
650 6 |a REST (Architecture logicielle) 
650 6 |a Hypertexte. 
650 6 |a Interfaces de programmation d'applications. 
650 7 |a APIs (interfaces)  |2 aat 
650 7 |a Application program interfaces (Computer software)  |2 fast  |0 (OCoLC)fst00811704 
650 7 |a Hypertext systems.  |2 fast  |0 (OCoLC)fst00965876 
650 7 |a Representational State Transfer (Software architecture)  |2 fast  |0 (OCoLC)fst01747417 
650 7 |a Software architecture.  |2 fast  |0 (OCoLC)fst01200416 
856 4 0 |u https://learning.oreilly.com/videos/~/9781491936511/?ar  |z Texto completo (Requiere registro previo con correo institucional) 
994 |a 92  |b IZTAP