Zope’s session management makes use of name-spaces like cookies, HTTP form elements, and/or parts of URLs “in the background” to keep track of user sessions.

Which of these name-spaces are used is configurable using the browser_id manager (described later).

Web Logic Server is set up to handle session tracking by default.

You need not set any of these properties to use session tracking.

The extended session ID format will be part of the URL if URL rewriting is activated, and the startup flag is set to true.

You can specify an interval of time after which HTTP sessions expire.

In other words, servlets have built in session tracking.[2] [2] Yes, we do feel a little like the third grade teacher who taught you all the steps of long division, only to reveal later how you could use a calculator to do the same thing.

But we believe, as your teacher probably did, that you better understand the concepts after first learning the traditional approach.

A server startup flag, -Dweblogic.Extended Session Format=true, retains the information that the load-balancing application needs for session stickiness.Session data is valid for the duration of a configurable inactivity timeout value or browser shut-down, which ever comes first.Zope’s session management keeps track of anonymous users as well as those who have Zope login accounts. Data maintained by Zope’s session management is no more secure than HTTP itself.is defined as a series of related browser requests that come from the same client during a certain time period.Session tracking ties together a series of browser requests—think of these requests as pages—that may have some meaning as a whole, such as a shopping cart application.