For example i do a submit.
a new page is displayed
then i do back
and submit again. That should be possible just fine.
But it is pretty much the same thing as i don't wait for the new page and press submit twice fast before the new pages comes in.
ofcourse if that is also not wanted we could easy insert a hiddenfield in a form and have a counter in that form and we test first
if it is the right value.
But what to do if it is detected?
On 4/23/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
All,
I have been contemplating this for a while, having it work in the background of my head. I think we might still have a problem with double submits.
First of all, we have solved the problem of the backbutton that does perform a post request. That is not a problem anymore, and IMO solved elegantly.
What is still a problem though is that when the submit of a form takes a while, or when the user advertently presses the submit button twice (the famous double click), wicket will still process the request twice.
Is this a Wicket framework concern or is it a application developer problem? Or is this something we might be able to check and prevent in a configurable manner? Something along the lines of a SingleSubmitForm extends Form in wicket-extensions that prevents this out of the box if possible at all?
Martijn
--
Wicket 1.2 is coming! Write Ajax applications without touching _javascript_!
-- http://wicketframework.org
