8/17/2019 Cuasibama

1/1

Cuasibama

Web Services expose their data and functionality trough resources identied

by URI ♣ Uniform Interface Principle: Clients interact ith resources through

a x set of verbs! "xample #$$P: %"$ &read'( P)S$ &create'( PU$ &update'(

*"+"$"♣

 ,ultiple representations for the same resource♣

 #yperlin-smodel resource relationships and valid state transitions for dynamic protocol

description and *iscovery

Prefer .ouns to /erbs ♣ 0eep your URIs short ♣ If possible follo a

1positional2 parameter3 passing scheme for algorithmic resource 4uery

strings &instead of the -ey5value6p5v encoding' ♣ Some use URI postxes

to specify the content type ♣ *o not change URIs ♣ Use redirection if you

really need to change them %"$ 7boo-8isbn596action5delete *"+"$"

7boo-79 ♣ .ote: R"S$ URIs are opa4ue identiers that are meant to be

discovered by folloing hyperlin-s and not constructed by the client ♣ $his

may brea- the abstraction ♣ Warning: URI $emplates introduce couplingbeteen client and server

%"$ is a read3only operation! It can be repeated ithout a;ecting the state

of the resource &idempotent' and can be cached! .ote: this does not mean

that the same representation ill be returned every time! ♣ P)S$ is a read3

rite operation and may change the state of the resource and provo-e side

e;ects on the server! Web brosers arn you hen refreshing a page

generated ith P)S$