Remy Maucherat wrote:
It will obviously use more CPU and make more API calls. However, it
does not allocate any objects, but instead will reuse per page objects
(which is very fast). So overall, it sounds weird to me that the
bottleneck would be on tag invocation.
In the end, it's hard to beat a Java "if" with a generic high level
construct ;) I don't understand how anyone could be surprised by that.
I think people are suprised because we don't realize that JSP is using
such a high level overhead internally. People see the semantics of c:if
and c:set and so forth and assume they're analogs for Java "if"
semantics and assume they would perform at the same level.
Its more obvious to you guys because you're usually delving into Tomcat
at that level where I haven't done so in a long time (especially into
Jasper generated source)l.
Kevin
--
Use Rojo (RSS/Atom aggregator)! - visit http://rojo.com.
See irc.freenode.net #rojo if you want to chat.
Rojo is Hiring! - http://www.rojonetworks.com/JobsAtRojo.html
Kevin A. Burton, Location - San Francisco, CA
AIM/YIM - sfburtonator, Web - http://peerfear.org/
GPG fingerprint: 5FB2 F3E2 760E 70A8 6174 D393 E84D 8D04 99F1 4412
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
