Gustavo Saramago wrote:
>
> Common issues like record pagination and connection
> pooling are frequent.
>
> As a result, we see many third party classes and tag
> libraries to address those issues and try to make our
> lives easier. This solves some problems an give us
> others: the right choices.
>
> I think that the folks at Sun would do a big favor to
> the community adding solutions to common issues in the
> JSP/Servlet/JDBC specs.
>
Connection pooling has already been addressed, the
newest versions of the JDBC have it built in. Of
cource, not everybody has the newest JDBC, but that's
a different issue.
Record pagination is harder, because the solution
depends heavily on the exact circumstances of the
application. (How many users, records expected per
user, size of hardware, programming budget, which
database is being used, how big is the db server,
etc).
So there isn't one single best answer. There isn't
even one or two best answers. It just depends.
So a big variety of third-party solutions, instead
of a single solution from Sun, is probably the right
thing.
That isn't to say the spec shouldn't move forward,
but for these two issues Sun seems to be doing ok.
--
Christopher St. John [EMAIL PROTECTED]
DistribuTopia http://www.distributopia.com
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
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