I wouldn't worry about it; there's a lot of caching going on inside AssetSourceImpl.
Don't prematurely optimize ... but plan to do real performance testing if you are expecting your application to be regurlarily saturated. Otherwise, keep your eyes on your database queries and let the rest shake out. On Fri, Jul 27, 2012 at 1:13 PM, Juan E. Maya <maya.j...@gmail.com> wrote: > Hello, > > first of all i am very glad to go back to work with T5 :) I was > missing the mailing list. :) > > I know the PerThread scope service are created per request, but i > don't want the object to be created for every asset that is loaded, i > only needed for the PageRender cycle. > Is there a way to avoid the extra instantiations ? > > Thank you > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
