> With regard to jsp and it's scalability, if you have one developer that is
> not as well versed at closing and killing a connection on one page, you
can
> lose all of your connection pooling in a matter of hours.
>
> Those are just things that CF takes care of for you.
>
> Jeff Steiner
Actually, while I would agree that this would be a bug, it also is true that
most large scale systems would not have web pages opening DB connections
anyway, connection pools or not. It's just a design issue that JSPs are
best used when they are related to presentation logic rather than handling
business logic, etc. The number of pages that might query something as
simple as a "hit count" can be large, but most architects would ensure that
such a "feature" would be written once and simply called (taglib, or simple
bean.getXX() method). This allows the implementation to change, to have the
number be memory resident rather than extracted from a database, or perhaps
calculated from a series of queries, or even having the database move to
another platform and not having to worry about changing EVERY page that
references the table directly. There is a benefit to reuse and
encapsulation and providing services to myriad front ends, not just
HTML-based desktop web browsers.
David
===========================================================================
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
