Servlet Session Tracking

• Sessions are maintained on the server side, and since HTTP is a stateless protocol, the web container cannot determine if the client intends to continue to use the web application.
• This is typical reequirement for web application, where a 'user activity' happens across multiple requests and responses, and the server is required to associate some form of uniqueness to each of the users.
• The server should be able to identify that a series of requests from a single client from a single working session.

There are four way to session tracking:

1. Cookies
2. Hidden Form Fields
3. URL Rewriting
4. Session using SSL