HTTP Session: Difference between revisions
Jump to navigation
Jump to search
| Line 24: | Line 24: | ||
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | <blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | ||
:[[Servlet Session Tracking API]] | :[[Servlet Session Tracking API]] | ||
</blockquote> | |||
=Session Implementation Details= | |||
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | |||
:[[JBossWeb/Tomcat HTTP Session Implementation Details]] | |||
</blockquote> | </blockquote> | ||
Revision as of 22:59, 31 May 2016
Internal
Overview
HTTP is a stateless protocol and maintaining a conversational state of the server is not directly supported by the protocol. HTTP provides no build-in way for a server to recognize that a sequence of requests originate from the same user. Since CGI, developers have been using various techinques to track the session: user authentication, hidden form fields, URL rewriting and persistent cookies. The servlet API brings improved support for session tracking. The support is built in top of the traditional techniques and it simplifies the task of session tracking in your servlets.
Example
- A HTTP Session Servlet https://github.com/NovaOrdis/playground/tree/master/jee/servlet/session-servlet