Академический Документы
Профессиональный Документы
Культура Документы
REST Fundamentals
Conclusion
Introduction
REST Fundamentals
Conclusion
Outline Introduction Web APIs REST Fundamentals HTTP REST Java Open Source RESTful Web Services Specication Implementation Conclusion Discussion Final word
REST Fundamentals
Conclusion
REST Fundamentals
Conclusion
REST Fundamentals
Conclusion
REST Fundamentals
Conclusion
REST Fundamentals
Conclusion
Introduction HTTP
REST Fundamentals
Conclusion
Introduction HTTP
REST Fundamentals
Conclusion
REST
HTTP
Introduction HTTP
REST Fundamentals
Conclusion
Client/Server Model
Introduction HTTP
REST Fundamentals
Conclusion
HTTP is resource-centric
Introduction HTTP
REST Fundamentals
Conclusion
Introduction HTTP
REST Fundamentals
Conclusion
Introduction HTTP
REST Fundamentals
Conclusion
HTTP Methods in more details GET PUT DELETE HEAD OPTIONS POST Safe The client did not request any side-effects on server other than data retrieval. Idempotent Any side-effects on the server of several identical idempotent methods are the same as the side-effects of one single method. Cacheable Explain in more details later. . . Safe, Idempotent, Cacheable Idempotent Idempotent Safe, Idempotent Safe, Idempotent
Introduction HTTP
REST Fundamentals
Conclusion
Intermediaries - Cache A new request for a cached resource can be returned immediately by intermediary caches.
Introduction HTTP
REST Fundamentals
Conclusion
Proxy an intermediary selected by a client, to provide interfaces to services like data translation, performance enhancement, or security protection. Gateway an intermediary imposed by the network or origin server to provide an interface encapsulation of other services, for data translation, performance enhancement, or security enforcement.
Introduction HTTP
REST Fundamentals
Conclusion
Stateless
HTTP Requests are stateless, which means each request is independent from the others.
Introduction HTTP
REST Fundamentals
Conclusion
Stateless
HTTP Requests are stateless, which means each request is independent from the others. intermediaries only need to work on a single interaction without knowing the entire topology
Introduction REST
REST Fundamentals
Conclusion
REpresentational State Transfer The representation returned by the server places or transfers the client from state to state. REST Architectural Style . . . a set of architectural constraints that, when applied as a whole, emphasizes scalability of component interactions, generality of interfaces, independent deployment of components, intermediary components to reduce interaction latency, enforce security, and encapsulate legacy systems. Roy T. Fielding
Introduction REST
REST Fundamentals
Conclusion
Introduction REST
REST Fundamentals
Conclusion
Introduction REST
REST Fundamentals
Conclusion
Introduction Specication
REST Fundamentals
Conclusion
Introduction Specication
REST Fundamentals
Conclusion
JAX-RS Hello Example import javax.ws.rs.GET; import javax.ws.rs.Path; import javax.ws.rs.PathParam; @Path("/hello/{username}") public class Hello { private String name="no-one"; @GET @Produces("text/plain") public String hello(@PathParam("username") String userName) { userName = userName==null?name:userName; return " Hello, "+userName; }
Introduction Specication
REST Fundamentals
Conclusion
@POST @Consumes("text/plain") public String hello(@FormParam("username") String userName) { name = userName==null?name:userName; return " Hello, "+userName; } }
Introduction Implementation
REST Fundamentals
Conclusion
Introduction Discussion
REST Fundamentals
Conclusion
REST Motivation
Introduction Discussion
REST Fundamentals
Conclusion
REST Fundamentals
Conclusion
REST Fundamentals
Conclusion
REST Fundamentals
Conclusion
REST Fundamentals
Conclusion