> Using session variables would be the better choice. I have just finished
a
> project where we used session variables to send the user to different
pages
> depending on different session values (i.e., how they came to the page,
what
> client site they came from, the type of transaction they wanted,...).
With
> JSP 1.0, the HttpSession is already defined, so you need only refer to
> "session.putValue(keyGoesHere)" and "session.getValue(keyGoesHere)."
>
Since it's a "stateless session bean", you may have a requirement to support
a client with multiple windows open, and each has to have a different state.
Since you can't do that with session variables (unless you add the page url
to the variable name - ick), another possibility is non-cached cookies.
_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
