Shrisha Radhakrishna wrote:
> Still, better (faster) than going through a servlet engine, don't u think
Not necessarily ... it depends on the implementation.
Consider that the JSP page's generated servlet will often be serving the template
text out of a byte array that is already in memory, so you bypass all the overhead
of opening and reading a disk file for each request (some OSs may buffer so you
don't need to go to physical disk every single time).
There are no absolute answers to a question like this.
>
> Imagine the JSP engine converting the .jsp to a .class only if scriplets are
> found. This is eseentially what IIS does (and, that's good).
>
That's certainly possible to do, but (for the reason cited above) I don't believe
you'd see any appreciable performance improvement on most servers.
Craig McClanahan
===========================================================================
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