Cargando…

REST API design rulebook /

In today's market, where rival web services compete for attention, a well-designed REST API is a must-have feature. This concise book presents a set of API design rules, drawn primarily from best practices that stick close to the Web's REST architectural style. Along with rules for URI des...

Descripción completa

Detalles Bibliográficos
Clasificación:Libro Electrónico
Autor principal: Massé, Mark
Formato: Electrónico eBook
Idioma:Inglés
Publicado: Sebastopol, CA : O'Reilly, ©2012.
Temas:
Acceso en línea:Texto completo (Requiere registro previo con correo institucional)

MARC

LEADER 00000cam a2200000Ia 4500
001 OR_ocn777401536
003 OCoLC
005 20231017213018.0
006 m o d
007 cr unu||||||||
008 120220s2012 caua o 000 0 eng d
040 |a UMI  |b eng  |e pn  |c UMI  |d CUS  |d COO  |d OCLCQ  |d DEBSZ  |d CNSPO  |d YDXCP  |d UNBCA  |d NLE  |d EBLCP  |d N$T  |d TEFOD  |d IDEBK  |d AU@  |d OCLCF  |d TEFOD  |d OCLCQ  |d E7B  |d S3O  |d OCLCQ  |d OCL  |d OCLCQ  |d FEM  |d NRC  |d OCLCQ  |d CEF  |d OCLCQ  |d UAB  |d OCLCQ  |d UKAHL  |d OCLCQ  |d OCLCO  |d OCLCQ  |d INARC 
019 |a 767502376  |a 859861905  |a 861530777  |a 880751154  |a 968097644  |a 969079983 
020 |a 1449317901 
020 |a 9781449317904 
020 |a 9781449319915  |q (electronic bk.) 
020 |a 1449319912  |q (electronic bk.) 
020 |a 9781449319908  |q (electronic bk.) 
020 |a 1449319904  |q (electronic bk.) 
020 |a 1449310508 
020 |a 9781449310509 
020 |z 9781449317904 
020 |z 9781449310509 
029 1 |a AU@  |b 000052897496 
029 1 |a DEBBG  |b BV040901651 
029 1 |a DEBSZ  |b 378290029 
029 1 |a DEBSZ  |b 381376915 
029 1 |a DEBSZ  |b 397165560 
029 1 |a GBVCP  |b 78543562X 
029 1 |a NZ1  |b 14872038 
035 |a (OCoLC)777401536  |z (OCoLC)767502376  |z (OCoLC)859861905  |z (OCoLC)861530777  |z (OCoLC)880751154  |z (OCoLC)968097644  |z (OCoLC)969079983 
037 |a CL0500000125  |b Safari Books Online 
037 |a FAF84AD7-CD96-46D4-92B1-90F960CA1C8A  |b OverDrive, Inc.  |n http://www.overdrive.com 
050 4 |a QA76.76.A63  |b M37 2012 
072 7 |a COM  |x 051370  |2 bisacsh 
082 0 4 |a 004.6  |2 23 
049 |a UAMI 
100 1 |a Massé, Mark. 
245 1 0 |a REST API design rulebook /  |c Mark Massé. 
246 3 |a Representational State Transfer API design rulebook 
246 3 |a Representational State Transfer Application Programming Interface design rulebook 
260 |a Sebastopol, CA :  |b O'Reilly,  |c ©2012. 
300 |a 1 online resource (xiii, 94 pages) :  |b illustrations 
336 |a text  |b txt  |2 rdacontent 
337 |a computer  |b c  |2 rdamedia 
338 |a online resource  |b cr  |2 rdacarrier 
347 |a text file  |2 rda 
588 0 |a Online resource; title from title screen (Safari, viewed Mar. 19, 2012). 
505 0 |a Table of Contents; Preface; Greetings Program!; Conventions Used in This Book; Using Code Examples; Safari® Books Online; How to Contact Us; Acknowledgments; Tim Berners-Lee; Roy Fielding; Leonard Richardson; O'Reilly Media, Inc.; Technical Reviewers; Colleagues; The REST Community; Stuart Rackham; Personal; Chapter 1. Introduction; Hello World Wide Web; Web Architecture; Client-Server; Uniform Interface; Identification of resources; Manipulation of resources through representations; Self-descriptive messages; Hypermedia as the engine of application state (HATEOAS); Layered System; Cache. 
505 8 |a StatelessCode-On-Demand; Web Standards; REST; REST APIs; REST API Design; Rules; WRML; Recap; Chapter 2. Identifier Design with URIs; URIs; URI Format; Rule: Forward slash separator (/) must be used to indicate a hierarchical relationship; Rule: A trailing forward slash (/) should not be included in URIs; Rule: Hyphens ( -- ) should be used to improve the readability of URIs; Rule: Underscores (_) should not be used in URIs; Rule: Lowercase letters should be preferred in URI paths; Rule: File extensions should not be included in URIs; URI Authority Design. 
505 8 |a Rule: Consistent subdomain names should be used for your APIsRule: Consistent subdomain names should be used for your client developer portal; Resource Modeling; Resource Archetypes; Document; Collection; Store; Controller; URI Path Design; Rule: A singular noun should be used for document names; Rule: A plural noun should be used for collection names; Rule: A plural noun should be used for store names; Rule: A verb or verb phrase should be used for controller names; Rule: Variable path segments may be substituted with identity-based values. 
505 8 |a Rule: CRUD function names should not be used in URIsURI Query Design; Rule: The query component of a URI may be used to filter collections or stores; Rule: The query component of a URI should be used to paginate collection or store results; Recap; Chapter 3. Interaction Design with HTTP; HTTP/1.1; Request Methods; Rule: GET and POST must not be used to tunnel other request methods; Rule: GET must be used to retrieve a representation of a resource; Rule: HEAD should be used to retrieve response headers; Rule: PUT must be used to both insert and update a stored resource. 
505 8 |a Rule: PUT must be used to update mutable resourcesRule: POST must be used to create a new resource in a collection; Rule: POST must be used to execute controllers; Rule: DELETE must be used to remove a resource from its parent; Rule: OPTIONS should be used to retrieve metadata that describes a resource's available interactions; Response Status Codes; Rule: 200 ("OK") should be used to indicate nonspecific success; Rule: 200 ("OK") must not be used to communicate errors in the response body; Rule: 201 ("Created") must be used to indicate successful resource creation. 
520 |a In today's market, where rival web services compete for attention, a well-designed REST API is a must-have feature. This concise book presents a set of API design rules, drawn primarily from best practices that stick close to the Web's REST architectural style. Along with rules for URI design and HTTP use, you'll learn guidelines for media types and representational forms. REST APIs are ubiquitous, but few of them follow a consistent design methodology. Using these simple rules, you will design web service APIs that adhere to recognized web standards. To assist you, author Mark Massé introduces. 
590 |a O'Reilly  |b O'Reilly Online Learning: Academic/Public Library Edition 
650 0 |a Application program interfaces (Computer software) 
650 0 |a Representational State Transfer (Software architecture) 
650 0 |a Web site development. 
650 0 |a Web sites  |x Design. 
650 0 |a Web services. 
650 6 |a Interfaces de programmation d'applications. 
650 6 |a REST (Architecture logicielle) 
650 6 |a Sites Web  |x Développement. 
650 6 |a Sites Web  |x Conception. 
650 6 |a Services Web. 
650 7 |a APIs (interfaces)  |2 aat 
650 7 |a COMPUTERS  |x Programming  |x Apple Programming.  |2 bisacsh 
650 7 |a Application program interfaces (Computer software)  |2 fast  |0 (OCoLC)fst00811704 
650 7 |a Representational State Transfer (Software architecture)  |2 fast  |0 (OCoLC)fst01747417 
650 7 |a Web services.  |2 fast  |0 (OCoLC)fst01173242 
650 7 |a Web site development.  |2 fast  |0 (OCoLC)fst01173243 
650 7 |a Web sites  |x Design.  |2 fast  |0 (OCoLC)fst01173252 
776 0 8 |i Print version:  |a Masse, Mark.  |t REST API Design Rulebook.  |d Sebastopol : O'Reilly Media, ©2011  |z 9781449310509 
856 4 0 |u https://learning.oreilly.com/library/view/~/9781449317904/?ar  |z Texto completo (Requiere registro previo con correo institucional) 
938 |a Internet Archive  |b INAR  |n restapidesignrul0000mass 
938 |a Askews and Holts Library Services  |b ASKH  |n AH26847673 
938 |a Askews and Holts Library Services  |b ASKH  |n AH26847672 
938 |a ProQuest Ebook Central  |b EBLB  |n EBL801433 
938 |a ebrary  |b EBRY  |n ebr10758620 
938 |a ProQuest MyiLibrary Digital eBook Collection  |b IDEB  |n cis28418002 
938 |a YBP Library Services  |b YANK  |n 11368642 
938 |a YBP Library Services  |b YANK  |n 7269322 
994 |a 92  |b IZTAP