@Retain are per-instance which can be much different than a static. @Retain looked like a good idea at the time, but I have never used it in a project.
Chances are, if you have some global state that needs to be shared between users, neither @Retain or a static field is correct ... a shared service is going to be a better option. On Wed, Jun 24, 2009 at 12:36 PM, Kalle Korhonen <kalle.o.korho...@gmail.com > wrote: > I was using @Retain for some fields that only needed to be initialized > once on a page. However, I see that they are reset after some time has > passed. How does the page pool work - are less used pages removed from > the pool only when other pages push them out or is the cache cleared > periodically? Are there any potential issues using static attributes > instead? > > Kalle > > --------------------------------------------------------------------- > 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 Director of Open Source Technology at Formos
