Jason Hunter wrote:
> Maybe. It works *way* faster for me because I can have the
> servlet/template catch its own output and resend that cache on later
> requests. Since my db query takes several seconds, this is a 99%
> speed boost. I just regen the page when my db changes. It's
> beautiful. JSP pages don't let you catch their output.
>
> You also can't GZip your JSP output on the way to the client. That's
> a trick servlets/templates can use to speed up slow connections.
>
Most of the Model2 examples I've seen have the servlet forwarding
to the JSP. What if you have the servlet including the JSP just
so that you can wrap things like the output and do other metadata
management?
In the JSP1.1 world you can do all kinds of wrapping of the
output using the bodyContent substreams. You can create a
top-level tag like <mytld:DBPage> that does nothing but wrap all
the rest of the page in a bodyContent substream that you could
then do the manipulations you describe above on. Is there more to
it than that?
Cordially from Corvallis,
Gabe Beged-Dov
--
http://www.jfinity.com/gabe
===========================================================================
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
