What I usually do is verify everything client-side with javascript to do all the fancy red letters and shaking or what have you, then make sure every piece of data is what I think it is, server-side, and return a generic error if it's not. That way clients get a full UI experience, and evil hackers get to spend more time figuring out how to attack my application :-P.
Probably not the best way to do it, but it works for me! Fitblip On Thu, May 24, 2012 at 6:53 PM, Bill Seitz <flux...@gmail.com> wrote: > Under lots of conditions, you want the outcome of server-side > rejection of a form to be > (a) send the user back to the form with all the data they entered > (b) stick a red error/alert message near the top > (c) possibly stick red alerts next to specific fields > > Is there a nice example app showing the smart way to do those? > > -- > You received this message because you are subscribed to the Google Groups > "web.py" group. > To post to this group, send email to webpy@googlegroups.com. > To unsubscribe from this group, send email to > webpy+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/webpy?hl=en. > > -- You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to webpy@googlegroups.com. To unsubscribe from this group, send email to webpy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/webpy?hl=en.
