session - Stateless with cookie vs statefull -



session - Stateless with cookie vs statefull -

i found sth this:

"stateful – maintain track of stored info used current transaction.

stateless – every transaction performed if beingness done first time. there no stored info used current transaction.

in purely stateless environment wouldn’t need session id. each request contain info server need process. many applications need maintain state maintain track of whether or not session authenticated view content or maintain track of user doing. wouldn’t want send user credentials on wire each request."

i'm quite confuse. if stateless session cookie maintain state it's mean that: stateless session cookie= session stateful ?

another think. found info session stateless client side session , stateful server side session. how can discuss client side session if stateless session not maintain session ? every answers.

in purely stateless environment dont need sessions or cookies.

both sessions , cookies used maintain state. question where. cookies maintain state on client while sessions maintain state on server.

also wiki

" of import note session state can transferred server service such database maintain persistent state period , allow authentication. "

so typically in stateless design, yes there no state bewtween client requests. every client request have sufficient info perform requested action. however, still need authentication / authorization client identified request headers (typically).

session stateless

Comments

Popular posts from this blog

Delphi change the assembly code of a running process -

json - Hibernate and Jackson (java.lang.IllegalStateException: Cannot call sendError() after the response has been committed) -

C++ 11 "class" keyword -