> 2) When you said use session itself to track user web activites, I am
> currently employing sessions to store user data, however, I can't seem to
> keep it alive long enough to do what I want to do.
>
Most servlet engines have a way of specifying the sessions
time-to-live. Another way might be to drop your own cookie to the
user. In the base class of your servlet application you can first check
for a session and if it is not found, check for a cookie. If the cookie
is found you create a session based on that. If no cookie is found then
you either create a new session or refer them to a login page depending
upon your application.
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
