Brian Sletten Bosatsu Consulting, Inc. brian@bosatsu.net

More documents

Recommendations

Info

Building RESTful Interfaces
What is Controversial URI Opacity How much meaning should there be in URIs? How do naming schemes affect intermediary processing? make the Web brittle? differ by language context? 47
Page 1 and 2: Applied REST Brian Sletten Bosatsu
Page 3 and 4: Agenda Why Do We Care? REST Concept
Page 5 and 6: WS-Dissatisfaction “Conventional
Page 7 and 8: Security Abominations Tunneling SOA
Page 9 and 10: SOA What? SOAP 1.2 and Doc Lit are
Page 11 and 12: If You Build It... ...they will use
Page 13 and 14: What is REST? REpresentational Stat
Page 15 and 16: Resource Abstraction Generality by
Page 17 and 18: Representation A particular deferen
Page 19 and 20: REST Verbs Design decision to minim
Page 21 and 22: POST Create a Resource 21
Page 23 and 24: DELETE Remove a Resource 23
Page 25 and 26: Why Not Apache? Tomcat? IIS? Jetty?
Page 27 and 28: RESTlet Lightweight Java-based REST
Page 29 and 30: The REST is History Concepts are ba
Page 31 and 32: Architectural Style “An architect
Page 33 and 34: Architectural Properties Of Interes
Page 35 and 36: Client-Server Supports Separation o
Page 37 and 38: Stateless All parameters travel wit
Page 39 and 40: Replication Decentralization of dat
Page 41 and 42: Uniform Interface Improves generali
Page 43 and 44: Layered System Managed dependencies
Page 45: REST Properties Based on figure fro
Page 49 and 50: Roy on URI Opacity "REST does not r
Page 51 and 52: Encoding Meaning in Structure Which
Page 53 and 54: Hierarchical + Non-Hierchical http:
Page 55 and 56: Pragmatic REST At a minimum, URIs m
Page 57 and 58: Real World Examples Amazon http://w
Page 59 and 60: Open Issues Describing RESTful serv
Page 61 and 62: Selling REST REST started off as th

Brian Sletten Bosatsu Consulting, Inc. brian@bosatsu.net

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?