On Mon, 12 Jul 2010 16:37:55 -0300, Howard Lewis Ship <[email protected]>
wrote:
Nearly all the code for this is in place. I'm going to be updating
some docs in the next couple of days, and trying to identify any
latent performance problems. I have some ideas for optimizations that
will speed up page loads minutely. I'm pretty happy with how this came
out!
This is awesome! It even makes understanding Tapestry easier, less
error-prone that it already is and less memory-consuming that it already
is.
How the initial values of fields (private List list = new List()) are
being treated? I guess it eliminates the field mutable initial value
problem (when it was kept after the page instance was returned to the
pool). If not, I suggest you to do so.
Do you have plans for performance benchmarks comparing 5.1, 5.2 with page
pool and 5.2 without a pool?
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
