I am carrying out some research into the use of HttpSession state in real-world
applications and am interested in collecting data on the following issues:
1. What is the typical/maximum size of application session state?
2. How many attributes are used to structure session state?
3. Are separate attributes used to partition mutable and immutable session
state?
3. How much of the state is modified in a typical request?
3. Is the application "distributable"?
4. If yes:
(a) when a modification is made to the state, does the servlet
indicate this to the container through setAttribute?
(b) Do you assume that any container failover mechanism preserves your
(serializable) session state exactly or do you code defensively?
I'd be very grateful for any answers to the above that you care to provide, and any
other comments that you have about the session state mechanism and its API.
Please reply to me directly off list.
Thanks
Mick Jordan
Sun Labs
___________________________________________________________________________
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
