Why don't you just disable the submit buttons in question when they submit? (set the disabled attribute to true)
On 11/15/06, Denis McCarthy <[EMAIL PROTECTED]> wrote:
Hi, I'm encountering a problem in my app where users are double submitting a form, creating a hibernate exception in the back end where two sessions are attempting to update the same collection. I've read some posts about preventing form resubmission by using a unique token in the form to detect a double submit. If a double submit is detected, the second and subsequent submits wait until the original one returns and then report the outcome of that transaction (if I understand correctly, it's the last submit that issues the response to the user, and the first one does the updating). I'm wondering a) is this indeed the right approach to stop users who are over-enthusiastic in their button clicking from encountering errors, and b) does anyone have an actual example of code that implements this pattern? Thanks very much Denis Mc. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tapestry/Dojo/(and a dash of TestNG), team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
