This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hi all: I have posted earlier about the usage of saveToken() and check isTokenValid(request) method. Because I wanted to make sure that the user doesn't click the "submit" button twice. I managed to achieve that, However what I want is the following:
suppose the user press the "submit" button more than once. The thread that executes the first request still runs, but has no means of providing its response to the browser. Hence, the user may be left with the impression that the transaction did not complete, while in reality, it may have successfully completed.
So I would like to know if there can be a complete solution that prevents duplicate submission and still ensures the display of a response that represents the original request's outcome.
I have indeed, and downloaded their example and I ran it on my local app server, it DOESN"T claim to do what it is supposed to do, I clicke on the "OK" button more than once, and the second request just brings me to an empty page, because the ActionForward object returns NULL.
So if anyone, has solved this problem before, please do let me know...
I'd truly appreciate it...
Again, I would like to thank everyone for their time in advance.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Urgent....please HELP....Different user Multiple submission problem