|
> From: Hatzenbeler, Tim > > I thought you only got the 1 time penalty with JSP's since they aren't > compiled, but with servlets there was no penalty, thats why I figured the > template engines were so popular, you could still seperate > presentation from > code, but not suffer the 1 time compiling penalty... A JavaServer Page is compiled once the first time anyone needs it. It is then available (in effect as a servlet) the next time anyone uses it. Note that this one-time cost is only incurred during development. Once the JSP is introduced into production, it will be compiled the first time anyone accesses it (which we would HOPE would be when it was tested by the person promoting it to production). From that point on, it will be available as a compiled servlet. Template approaches work fine, but there is the issue of loading the templates and parsing them. Loading can conceivably be cached, but parsing still penalizes you every time - at best you can reduce the time down to a number of hashtable lookups, but it's still relatively expensive compared to the compiled JSP. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
