|
Building servlets with session tracking
This tutorial teaches techniques for building Internet applications using servlet and JSP technology. A key point is to enable session handling, so the servlet knows which user is doing what. The tutorial shows a URL bookmarking system in which multiple users access a system to add, remove, and update an HTML listing of bookmarks. The servlet uses JSP technology to handle the user interaction.
|
|
Introduction to Sessions
In the client/server and Web application world, a session can be considered as a series of related interactions between a single client and the server that take place over a period of time.
|
|
WebSphere Application Server Best Practices using HTTP Sessions
A session is a series of requests to a servlet, originating from the same user at the
same browser. Sessions allow JSPs running on a JSP engine to keep trac of individual users,
a concept known as personalization.
|
|
Alternatives to servlet session management
In this installment, Thomas Davis and Craig Walker demonstrate the power of the RSEF framework by implementing a wrapper that gives you greater control over session management. Session state can be stored in the browser, in the server's memory, or in the database.
|
|
Building servlets with session tracking
This tutorial teaches techniques for building Internet applications using servlet and JSP technology. A key point is to enable session handling, so the servlet knows which user is doing what. The tutorial shows a URL bookmarking system in which multiple users access a system to add, remove, and update an HTML listing of bookmarks. The servlet uses JSP technology to handle the user interaction.
|
|
Session Tracking
HTTP is a stateless protocol: it provides no way for a server to recognize that a sequence of requests are all from the same client. Privacy advocates may consider this a feature, but it causes problems because many web applications aren't stateless. The shopping cart application is a classic example--a client can put items in his virtual cart, accumulating them until he checks out several page requests later. Other examples include sites that offer stock brokerage services or interactive data mining.
|
|
Servlet Session Tracking
Session tracking is a mechanism for building a sophisticated state-aware model on top of the web's stateless protocol. With session tracking, the server maintains session state through the use of cookies or URL rewriting.
|
|
Session Tracking with Servlets
HTTP is a “stateless” protocol: each time a client retrieves a Web page, it
opens a separate connection to the Web server, and the server does not automatically
maintain contextual information about a client. Even with servers
that support persistent (keep-alive) HTTP connections and keep a socket
open for multiple client requests that occur close together in time (see Section
7.4), there is no built-in support for maintaining contextual information.
|
|
Manage distributed sessions
Using RMI and the Proxy API introduced in JDK 1.3, this article describes a technique that allows one or more servlet servers to maintain session information on one or more session servers.
|
|
Using the HttpSession object of the Servlet API
The Java Servlet API represents an elegant and powerful way to shift processes from client to server, and offers a number of advantages over CGI. These advantages have certainly been enumerated so that most developers are aware of the servlet advantage. However, some of the details of the servlet architecture may at first seem daunting. Here's a short introduction on one aspect of writing servlets: the HttpSession object.
|