Actually, splitting hairs, I would call field persistence the heavier option ... you just don't see all the machinery it takes to make it work.
On Wed, May 19, 2010 at 1:20 PM, Thiago H. de Paula Figueiredo <thiag...@gmail.com> wrote: > On Wed, 19 May 2010 17:04:25 -0300, Pete Poulos <pete.pou...@gmail.com> > wrote: > >> I considered this, but the documentation for SessionState makes it >> sound like it is a very heavy handed solution, > > Why? Just curious. :) > >> Whereas, the >> documentation for Flash Persistence makes it sound like the right fit. > > It surely fits. :) > > -- > 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: 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
