Costin Manolache wrote:
Kin-Man told me it wasn't done yet (he mentioned the curent methods should stay, though), unfortunately. From what he said, he needed to write more tag plugins to see if he was able to implement JSTL tags with the current API.Hans Bergsten wrote:Costin Manolache wrote:[...] In an ideal world, all "core" tags would be recyclable and garbage-free - that may allow them to run at comparable speed with a hard-coded page.I think it's more important to implement "open coding" of JSTL, i.e. generate if and for statement instead of using <c:if> and <c:forEach> tag handlers. That would really make a difference for all apps that use JSTL, while the potential gains from tag handler reuse depend on a lot of factors that varies between applications and the runtime environment.
+1 - "open coding" is far better ( for performance ). Is the API/model
for portable open coding defined and stable ? That would be by far the biggest improvement in JSP performance.
I agree it's definitely a good way to get around the problems with tags without adding too much complexity. In the end, I decided to talk about it a bit in a chapter of my book.
What's really funny is that you can get rid of the tag handler, and write only the tag plugin. That's of course, if you don't care about portability, and you have the tag plugin able to handle all forms of you tag.
But for people who use regular tag handlers - I think we need to fix
the tag pool, and a fixed tag pool will improve the performance significantly. And if regular tags are used, for whatever reason, recycling should be taken into account - if people care a bit
about performance.
+1. Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
