On Mon, 07 Feb 2011 15:01:34 +0100, Massimo Lusetti <[email protected]>
wrote:
On Mon, Feb 7, 2011 at 9:17 AM, Howard Lewis Ship <[email protected]>
wrote:
2) The ValidationTracker object would no longer have to reside in the
session, which in many applications can significantly defer the
creation of the session, improving throughput
This would be more then enough for me.
Stateless form validation by default would be great, I'm doing this right
now with PageValidationExceptions as described in this post:
http://www.mail-archive.com/[email protected]/msg38031.html
In order for that to work with Tapestry's built-in validation mechanisms,
the Form component needs a small patch to throw a PageValidationException
whenever the ValidationTracker contains errors.
All forms can then be completely stateless, and pages can also be made
cachable for a long time.
Tapestry's current default behaviour will redirect back to the same URL
when displaying form errors, which won't work very well unless you prevent
client side caching with appropriate HTTP headers.
How do you guys feel about changing the non-ajax form behaviour to use the
PageValidationException approach above, and render a response directly in
case of form errors?
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
