On Thu, 24 Feb 2011 22:52:12 +0100, Thiago H. de Paula Figueiredo
<[email protected]> wrote:
On Thu, 24 Feb 2011 18:22:13 -0300, Martin Strand
<[email protected]> 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?
Sure, but then I suppose regular session storage would work equally well.
Patching the Form component to prevent redirects on validation errors
means we don't have to bother setting up clustered sessions only to
display these error messages. :)
Most importantly, with this change to the Form component's behaviour we
can now make pages cachable but still be able to show validation errors.
Proper caching can give an enormous performance boost, especially when
combined with a caching proxy such as Varnish or Squid.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
