I have a question about implementation that I'd love some input on.
The Problem:
I have a web application that has to return variable length resultsets,
sometimes quite large (a few 100 rows max). There are several tables that
might return large resultsets and each gets viewed in a different area of
the website. I need an efficient way to allow a user to navigate through
these resultsets.
What I'm doing right now is instantiating a Bean to perform the query and
store the resultset. The controller then passes off to a jsp that displays
the first x elements of the resultset vector. Clicking a next/previous
button goes forward and back through the set. The problem with this method
is that there is not elegant way of disposing of the bean when the user
navigates to another part of the website. If there are several of these
resultset beans hanging around it leads to a lot of wasted memory.
If anyone has some insights they would care to share, I'd greatly appreciate
it.
Donald
===========================================================================
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
