Refuge’s Session State Reconsidered
Web applications are built using a stateless protocol called HTTP/S. Because of this, the web server retains no relationship between transactions. Each time a client makes a request to the web server, the requests are treated independently and in isolation from transactions that came before or that will happen after the request. All the information required for the server to respond must be provided by the client in each request.
Because web applications are built upon a stateless protocol, applications often need a mechanism to tie or relate user actions and data (that is, state) across multiple, stateless transactions. This mechanism is commonly called session state.
Session state may be used to track ...
Get Scalable Cloud Ops with Fugue now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
