In your situation, you probably don't want to mess around with the
HttpSession object. The session object is designed for sharing info
within the same session, not the same user. If sharing info among
multiple sessions is desired, use ServletContext instead. One solution
would be store your user
> From: Daniel Guggi [mailto:[EMAIL PROTECTED]
> I ran into a session-issue with a webapp. There are situations when it
> would be nice for a user (same browser/same machine/same
> webapp) to have
> the possibility to login twice and thus have two different
> JSESSIONIDs.
If you use cookies to
