On Jun 1, 2009, at 8:08 AM, Leon Rosenberg wrote:
On Mon, Jun 1, 2009 at 1:37 PM, Robert Koberg <r...@koberg.com> wrote:
On Jun 1, 2009, at 7:12 AM, Tim Funk wrote:
The key is making sure you have the ability to log how long differnt
things take. (And the ability to turn them on or off) Otherwise
you are
flying blind.
I think you can generally say that the less you have to do on the
server,
the better. If you can generate out a page *as much as possible* so
that
only the really necessary dynamic components are created at
runtime, then it
is better.
We use XSL/XML to pregenerate a JSP bringing all known page
content/components.
I don't see why you would be flying blind. Seems like a no-brainer.
Funny :-)
I remember removing xml/xsl generation from the chain and replacing it
with jsps a while ago. Brought about factor 10 performance (from 50 ms
rendering time to 5). So I second TIm's statement: measure first and
measure after. And compare :-)
No. It is not in the chain, well, not in the runtime chain/pipeline.
It is generated before you even put it on the live server.
-Rob
Leon
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
