In session tracking all the session information is with the server only and
just an ID is sent to the client (browser e.g.). In cookies the whole of
session information is kept with the browser on the persistent store. So
when u use cookies network traffic is higher and in case of servlet session
tracking more data has to be stored on server. There are cases when u cannot
assume that cookies are enabled on browser. OK. That means when cookies are
disabled even then i can use Servlet Session Tracking? Why should i go for
cookie? Can it be so that browser dont support Servlet Session Tracking i.e.
not keeping the Session ID with them.
Hope i am clear.
V
___________________________________________________________________________
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
