In a Session Object when I use the setAttribute method how much of data or how many objects can I store in a session object.
Randall Twede
Ranch Hand
Joined: Oct 21, 2000
Posts: 3901
posted
0
hmm. I dont know. I used putValue(); instead I am unfamiliar with setAttribute() can anyone explain the difference to me?
I never took notes in college. That's how I got a 4.0 the first 2 years, and a 3.5 the second two years.
Peter den Haan
author
Ranch Hand
Joined: Apr 20, 2000
Posts: 3252
posted
0
Originally posted by Randall Twede: hmm. I dont know. I used putValue(); instead I am unfamiliar with setAttribute()
putValue() has been deprecated in v2.2 of the Servlet spec. setAttribute() is a straightforward replacement of it. Ditto getValue() and removeValue() versus getAttribute() and removeAttribute(). Regarding the original question, there is no fixed limit to the number and size of objects you store in the session. Of course, your application will need lots of iron if your session-bound objects are many and/or bulky. 24/7 environments typically use clustering with session fail-over, which implies that everything you bind to the session is replicated into a safe location. Therefore there may be more overhead to storing something in the session than you might realise. - Peter
[This message has been edited by Peter den Haan (edited March 08, 2001).]
0
