I found the servlet-interest archives and found a trail of discussion on the topic. Sorry if this question is old news. The consensus is that the JVM stores the session data in general RAM. Therefore, there is no real technological limitation of storing objects in the session. However, I sense there is more to the story. For example, under certain conditions the session objects may have to be serialized. One archive message said that it is the serialization itself that causes a lot of overhead processing. The serialization seems to happen either when multiple web servers are used, or for RMI calls. The EJB spec says to make session objects serializable. I would still like to hear your comments. . . . . . . . . . . . . . . . . Dave Whaley Developer, Web Applications Robert Half International, Inc. [EMAIL PROTECTED] . . . . . . . . . . . . . . . . ___________________________________________________________________________ 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
