This document provides an overview of REST (Representational State Transfer), including its core concepts and how to build RESTful web services. The key points are: 1) REST uses resources identified by URIs, and representations of those resources can be transferred via HTTP. 2) RESTful services use standard HTTP methods like GET, PUT, POST and DELETE to operate on resources in a stateless and uniform way. 3) Building stateless, cacheable and layered services allows REST architectures to scale up to internet scale.

1. Dian Wahyu Aditya [email_address] REST v 2.3

2. Agenda REST Overview

3. Core Concept

4. Web Service Demo Struts2

5. Spring MVC

6. Android Client

7. REST? Representational State Transfer # Defined by Roy T. Fielding in his doctoral dissertation. (Co-founder of Apache HTTP Project) An Architectural Style

8. REST? Representational State Transfer #Use HTTP, URI, and other web standard correctly Web Used Correctly

9. REST CORE CONCEPT

10. REST: Core Concept “ Things are Resources” Resources can be items of information (a blog entry) or informational descriptions of real things (a blog author) RESOURCE

11. REST: Core Concept “ Resource Have URIs” Uniform Resource Identifier are unique ids for resources. RESOURCE U R I

12. REST: Core Concept “ Resources have Representation” Representations can have different formats (HTML, XML, JSON). RESOURCE U R I REPRESENTATION REPRESENTATION

13. REST: Core Concept “ Representations have URLs” Uniform Resource Locators describe how to get to a representation of a resource, they include protocol, hostname, path and extra information. RESOURCE U R I REPRESENTATION REPRESENTATION URL URL URL

14. REST: Core Concept “ Client interact via Verbs” RESOURCE U R I REPRESENTATION REPRESENTATION URL URL URL POST GET PUT DELETE

15. RESTFul Web Service

16. RESTFul Web Service “ Use HTTP Standard Methods” Retrieve GET Update PUT Create POST Remove DELETE

17. RESTFul Web Service “ Use Standard Methods / Uniform Interface” Safe GET Idempotent PUT Idempotent DELETE

18. RESTFul Web Service “ Use Standard Methods / Uniform Interface” Safe method # There are no side-effects # The requested resource stays unmodified Idempotent # Issuing the same request multiple times yields the same result

19. RESTFul Web Service “ All About the URIs” http://blog.mervpolis.com/roller/dwx http://blog.mervpolis.com/roller/dwx/category/Java http://blog.mervpolis.com/roller/dwx/date/201009 http://blog.mervpolis.com/roller/dwx/entry/hibernate_event_listener Directory Structure-like URIs To the Point Easy to Guess

20. RESTFul Web Service GET /deleteuser?name=Robert HTTP/1.1 DELETE /user/Robert HTTP/1.1