As Jim Haungs is fond of saying, "the only interesting numbers are one and
infinity". Designing a workaround for exactly two sessions could cause
problems when you need to go to three...
Also, note that if a user starts a new browser process, that browser will
get a new session no matter what you do. In fact, that's how I support
multiple sessions -- if people want multiple logins, they start up multiple
browsers instead of doing file->newWindow.
In your case, you apparently want multiple sessions in the same browser
instance -- much trickier. Perhaps you could create a simple session
management bean that listens for the session binding event, and initializes
a Hashtable of sub-sessions? If you're using model2 architecture, you could
guarantee that all served pages include a sub-session identifier in their
URLs. I'm not sure how you'd support creation of new sessions -- perhaps
through an explicit menu item in your app?
_3
M
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
