|
|
|
|
| LEADER |
02790nmm a2200385 u 4500 |
| 001 |
EB001943103 |
| 003 |
EBX01000000000000001106005 |
| 005 |
00000000000000.0 |
| 007 |
cr||||||||||||||||||||| |
| 008 |
210123 ||| eng |
| 050 |
|
4 |
|a QA76.754
|
| 100 |
1 |
|
|a Amundsen, Michael
|
| 245 |
0 |
0 |
|a REST, hypermedia, and the semantic gap
|b why "RMM-level3 REST" is not enough
|c with Mike Amundsen
|
| 246 |
3 |
1 |
|a Representation state transfer, hypermedia, and the semantic gap
|
| 260 |
|
|
|a [Place of publication not identified]
|b O'Reilly Media
|c 2015
|
| 300 |
|
|
|a 1 streaming video file (51 min., 2 sec.)
|b digital, sound, color
|
| 653 |
|
|
|a Representational State Transfer (Software architecture) / fast / (OCoLC)fst01747417
|
| 653 |
|
|
|a Hypertext systems / http://id.loc.gov/authorities/subjects/sh88002671
|
| 653 |
|
|
|a Hypertexte
|
| 653 |
|
|
|a Application program interfaces (Computer software) / http://id.loc.gov/authorities/subjects/sh98004527
|
| 653 |
|
|
|a APIs (interfaces) / aat
|
| 653 |
|
|
|a Application program interfaces (Computer software) / fast / (OCoLC)fst00811704
|
| 653 |
|
|
|a REST (Architecture logicielle)
|
| 653 |
|
|
|a Software architecture / http://id.loc.gov/authorities/subjects/sh2004001071
|
| 653 |
|
|
|a Architecture logicielle
|
| 653 |
|
|
|a Interfaces de programmation d'applications
|
| 653 |
|
|
|a Representational State Transfer (Software architecture) / http://id.loc.gov/authorities/subjects/sh2009000706
|
| 653 |
|
|
|a Software architecture / fast / (OCoLC)fst01200416
|
| 653 |
|
|
|a Hypertext systems / fast / (OCoLC)fst00965876
|
| 041 |
0 |
7 |
|a eng
|2 ISO 639-2
|
| 989 |
|
|
|b OREILLY
|a O'Reilly
|
| 500 |
|
|
|a Title from title screen (Safari, viewed August 25, 2015). - Date of publication taken from resource description page
|
| 856 |
4 |
0 |
|u https://learning.oreilly.com/videos/~/9781491936511/?ar
|x Verlag
|3 Volltext
|
| 082 |
0 |
|
|a 000
|
| 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
|