I'm also very curious about this.
What we do here (using GNUJSP) is have a servlet read all the input, do the
work, and create a bean with all the output variables to substitute. It
puts this bean in the HttpSession and does an
HttpServiceResponse.sendRedirect() to the JSP which uses the bean. This
seems like it would be _terrible_ for performance, not only because it
involves two separate HTTP requests per page but also because it involves
completely unnecessary HttpSession operations.
Does anyone have any performance benchmarks on this vs. "model 1" vs. the
standard templating model to which Keith was referring? Does the 0.92
getRequestDispatcher() stuff address these issues?
-Ben
At 02:58 PM 3/15/99 +0000, Keith Kwiatek wrote:
>one more thing.... the purpose of my original post was also to flesh out
in my
>own mind the JSP "model 2" flow.+ performance with regards to HTML/code
>separation....... My understanding is that in the JSP model 2, a servlet
takes a
>requests, goes to the database to fetch some rows, encapsulates them in a
bean
>and then somehow calls a JSP page which uses macro template language to
format
>the bean into html......
>
>compare this to a servlet reading in a template at init time (Once), and
parsing
>the macro variables/constructs (Once)..... and then anytime it gets a request
>and fetches DB rows, it simply does variable substitution on the template and
>outputs it....
>
>Please enlighten me...
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
