On Thu, 24 Feb 2011 18:22:13 -0300, Martin Strand
<do.not.eat.yellow.s...@gmail.com> wrote:
Just wanted to bring this up since the Form component is currently the
only part of Tapestry that we need to patch for our stateless
application.
In this scenario, have you considered the option of implementing a
PersistentFieldStrategy that uses an in-memory database instead of the
session to override the default flash persistence implementation?
--
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: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
