Ryan Grange wrote:
> How well would this methodology deal with people who double-click on
> submit buttons?
Of course, second submit generates second POST.
For browser history that looks like user clicks "Back" and then clicks
any other link on a page.
Everything else depends from your application and transaction processing
mechanism.
If submit processing could be treated as one transaction that's good and
you can handle it as a second transaction.
If submit processing is a part of larger transaction you should decide
what does it mean within your application (change some data posted early
or add something).
In any case second click on submit is explicit user action, which can
not be considered as anything else then second submit.
With best regards,
Alexander Veremyev.
--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
