That would be nice to have tag pooling in 4.x. It was one of those things that I wanted to do before my day job changed a little. Anyway, a few thoughts:
Tag pooling as implemented in 3.x is IMHO a good starting point, but generated code will really benefit if we can handle the more "traditional" optimizing compiler situations like pulling redundant code (i.e. tag setter methods) out of loops, etc. Hopefully, with the recent talk of new jasper (very exciting), we can have a good place to easily integrate such optimizations. If you have specific questions about 3.x tag pooling, just let me know... I might be able to remember some of it. -casey peter lin wrote: > > thanks larry for that information. I will take a look before I jump in. > > Larry Isaacs wrote: > > > > This was done by Casey Lucas. However, be aware that it comes > > with a disadvantage in that because of the extra code, it reduces > > the number of tags you can get on a JSP be for you hit Bug #6088 > > > > <http://nagoya.betaversion.org/bugzilla/show_bug.cgi?id=6088> > > > > I'm doubtful you can get 100-300 tags on a JSP page in any version > > of Jasper. Also, check recent posts on this list for a proposed > > "Jasper2" effort that is underway. See: > > Actually, I managed to make a page with about 140 tags that barely > squeezes under the 64K limit. Under moderate load it runs like a dog. > When I break it up into smaller pages using action include, it runs much > better. > > > > > <http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg24054.html> > > > > Cheers, > > Larry > > > > Peter lin > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
