-----Original Message-----
From: Phillips, George H. [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 03, 2000 9:32 AM
To: [EMAIL PROTECTED]
Subject: Re: JSP Architectural Question
All of the architectures I've read about on this list are very logical,
maintainable, and seem to make good use of the resources provided by Java -
but what do they do to the execution speed of the app vs. a "plain" JSP
implementation which mostly uses just the server pages? Do the efficiencies
of using servlets/beans/ejbeans etc. make for a faster running overall
process, or is there a tradeoff here of execution time for flexibility and
maintainability?
No, there is a tradeoff. In my architecture, I plan to use EJBs in certain
places, straight JDBC calls in others. What I gain in using the EJBs is the
support of transactions on updates. However, it eats up more CPU cycles,
adds another layer of complexity, something else that can tip over and go
'BOINk'. I am creating this prototype for a client who maintain a multitude
of e-commerce web sites, so flexibility, maintainability, and transactional
integrity is key. A single website with X number of pages may be able to
use straight JSPs without the complexity being discussed. It is the
tradeoff between C and Java. How close to the metal do you need to be?
Perry Hoekstra
===========================================================================
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
