Examples[edit]
An HTTP server can understand each request in isolation.[2]
Contrast this with a traditional FTP server that conducts an interactive session with the user. During the session, a user is provided a means to be authenticated and set various variables (working directory, transfer mode), all stored on the server as part of the session state.
Stacking of stateless and stateful protocol layers[edit]
There can be complex interactions between stateful and stateless protocols among different protocol layers. For example, HTTP, a stateless protocol, is layered on top of TCP, a stateful protocol, which is layered on top of IP, another stateless protocol, which is routed on a network that employs BGP, another stateful protocol, to direct the IP packets riding on the network.
This stacking of layers continues even above HTTP. As a workaround for the lack of a retained session state, HTTP servers implement various session management methods,[3] typically utilizing a session identifier in an HTTP cookie referencing a session state stored on the server, effectively creating a stateful protocol on top of HTTP.[4] HTTP cookies violate the REST architectural style because even without referencing a session state stored on the server, they are independent of session state (they affect previous pages of the same website in the browser history) and they have no defined semantics.[5]
$_$_$DEEZ_NUTS#10__titleDEEZ_NUTS$_$_$
$_$_$DEEZ_NUTS#10__subtextDEEZ_NUTS$_$_$
$_$_$DEEZ_NUTS#13__titleDEEZ_NUTS$_$_$
$_$_$DEEZ_NUTS#13__subtextDEEZ_NUTS$_$_$
$_$_$DEEZ_NUTS#11__titleDEEZ_NUTS$_$_$
$_$_$DEEZ_NUTS#11__subtextDEEZ_NUTS$_$_$
$_$_$DEEZ_NUTS#12__titleDEEZ_NUTS$_$_$
$_$_$DEEZ_NUTS#12__subtextDEEZ_NUTS$_$_$