web - Does ST(State Transfer) in REST mean that state must be held by client? -


i read what “state transfer” in representational state transfer (rest) refer to? , several post or videos rest, , know 1 of constraint of rest stateless.

  1. according many posts http://www.restapitutorial.com/lessons/whatisrest.html ,to make architecture stateless, client must hold enough information server right thing, means server not have client state. mean build rest application through putting user state in client cookie?

  2. but according many posts pros , cons of sticky session / session affinity load blancing strategy? , can make stateless application storing user data in database or memcache, avoid storing session in application server. if try approach, can make rest architecture?

the idea of honest rest service allow easy communication client, client not in web browser: mobile or desktop application or else. so, each request service must provide necessary information process request. keeping state on server complicate task, because clients not control it.

so, yes, ideally state must held clients. but, need understand mean "state". because there different kinds of state out there: application state, , resource state. following article distinction.

p.s. , btw, keeping state in cookies complicate life clients well(if not web-browsers).


Comments

Popular posts from this blog

java - Oracle EBS .ClassNotFoundException: oracle.apps.fnd.formsClient.FormsLauncher.class ERROR -

c# - how to use buttonedit in devexpress gridcontrol -

nvd3.js - angularjs-nvd3-directives setting color in legend as well as in chart elements -