Hi,
Fat sessions bloat the servlet environment and fat cookies jam the network
pipeline. The best solution if you want to store large-sized session data
is to have the Session object contain a primary key pointing to a database
row.
Gene
-----Original Message-----
From: A mailing list for discussion about Sun Microsystem's Java Servlet
API Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of
Godbey, David
Sent: Wednesday, July 12, 2000 12:44 PM
To: [EMAIL PROTECTED]
Subject: Session objects or cookies?
A colleague of mine objects to using session objects to stash information
because he claims it bloats the servlet environment. He prefers, instead, to
stash the info in the cookie.
What is the conventional wisdom on this?
Dave Godbey
___________________________________________________________________________
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
___________________________________________________________________________
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
