Thanks you all for the suggestions. I think I understand the problem. BJ - What I don't quite understand is what serialization will achieve. Do you mean that I should serialize the object to check variables by reading them?
PS. I only noticed this when I was implementing a connection pool and checking its effect..., and thinking that the code was buggy. Regards CARL -----Original Message----- From: A mailing list for discussion about Sun Microsystem's Java Servlet API Technology. [mailto:[EMAIL PROTECTED] Behalf Of BJ Jani Sent: 11 March 2003 05:04 To: [EMAIL PROTECTED] Subject: shared session object Hi Carl Do you Serialized the Session Object? then it won't overwrite> BJ ___________________________________________________________________________ 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 __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com ___________________________________________________________________________ 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
