> Everything you can absolutely put into the db, so use pl/sql. What you > cannot, use something else ...
I can't agree with this approach. If you have many users using your web application, regardless if that is used for internal application, e-commerce site or whatever, you can always add more application servers, but you can't do that so easily with your database server. In that case database server is your bottleneck and you don't want to slow database even more, which will be result of business logic inside database server. You will still have a need for store procedures and triggers but as exception, not as a rule. Of course, design depends on requirements, but in most cases I will recommend J2EE instead of pl/sql (or TransactionSQL or whatever). --Srdjan -------------------- Srdjan Pantic ASU Solutions, Inc. 3333 Bowers Ave, # 160 Santa Clara, CA 95054 phone (408) 654 7827 fax (408) 654 7820 =========================================================================== 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://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com
