>>> Gene Chuang <[EMAIL PROTECTED]> 12-Jul-00 11:02:21 PM >>>
>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.
Nonsense.
If you do that you have a fat session (a Connection ort a file handle
is a big thing) AND slow access. That mightr be okay sometimes, eg: if
there's a lot of flat data.
But the BEST solution is to think about the data you need to manage
for each request.
Think about:
- how much data there is
- what the data does
- whether the data is really an object
- what methods might operate on the data that might be an object
and then implement your code.
Don't be affraid of putting stuff on sessions. That's what they're
there for.
However - don't take it that it's a good idea to store the life works
of shakespear on every session because that would be a bad idea.
Design a solution for the problem at hand - one size does NOT fit
all.
Nic Ferrier
___________________________________________________________________________
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
