Glenn Nielsen wrote:
> I just had an idea (dangerous things) regarding tag pooling optimizations.
>
> When Jasper translates a page it should be able to generate information
> about which tag handler classes it needs, and for each tag handler, the
> profile of the attribute/value pairs. At runtime Jasper could make one call
> to a tag pooling synchronized method to get all available instances of the tag
>handlers
> it needs. Any tag handlers/attribute profiles it couldn't obtain, it would have
> to create. Then it would manage its own local tag pool during the execution
> of the request. On termination of the request, after the page has been committed
> to the remote client, it would make one call to a tag pooling synchronized
> method to recycle/add the tag handlers it used. So there would only be 2
> synchronized methods per page for implementing tag pooling regardless of
> how many tags are used. And you have the benifits of minimizing JVM memory
> usage by sharing a global JVM tag pool.
I would be ok with that, as long as I can set the size of the pool to be
zero, since I don't trust Java coders to outperform the optimizations
done by the JVM as outlined in earlier posts.
/Rickard
--
Rickard Öberg
Software Development Specialist
xlurc - Xpedio Linköping Ubiquitous Research Center
Author of "Mastering RMI"
Email: [EMAIL PROTECTED]
