Kevin Duffey wrote:
> I have a couple of things to say about this. First, the use of sessions IS
> a good thing in my opinion to allow a client to go from one page to the
> next while keeping track of items in a cart, for example. However, on our
> site, we do it slightly different. We use a "temporary" session that is put
> in the main HttpSession. That is, we have several "sections" of our site
> that use a single servlet to return multiple pages (using a hidden
> field/value deal to determine where in the current servlet they are..so as
> to return the next page in sequence properly). When a client hits this
> page, it creates the "page session" in memory, and stores it in the
> HttpSession. As they move from page to page it adds/modifies things in that
> temporary session object. When the last page is received, it destroys that
> object, since it is no longer needed.
I'm not sure what your session within a session accomplishes? Is this so
that you can assign null to the session within a session object when you're
done? Do you actually put an HttpSession inside of the HttpSession object?
> When the last page is received, it destroys that object, since it is no longer
> needed.
How do you do this? Java doesn't support the destroying of objects.
Mike
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
