Re: tapestry critique

>The creation of new objects is universally accepted as the 
number one cause
>for performance problems in Java.

That is not true, nor "universally accepted" - at least not 
in the sense that pooling is a solution. Unless you have huge 
objects which need extensive external resources to be 
operational, the effort spent on pooling will easily and by 
far exceed that for re-instantiation. After all, the JVM and 
garbage collector already do a kind of pooling for you.

regards,
Christian


-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/