Dirk
2006/4/24, Martijn Dashorst <[EMAIL PROTECTED]>:
I see a lot of possible solutions, but is this actually a framework concern?
MartijnOn 4/24/06, JasonB < [EMAIL PROTECTED]> wrote:Johan Compagner wrote:
> the problem i see is how to really detect a double submit that we
> don't want.
Please forgive me if this is already in the framework and I just haven't
needed to look for it...
In the case where the user submits twice quickly in succession, and the
first submit is still being processed, then my preferred behavior would
be to have the second submit join the currently processing first submit,
and to receive the output from that. (Aka: only do the work once)
This could later be extended to handle 'Now Processing Your Request'
pages that self-refresh waiting for the long submit process to complete
(think searching in travel sites).
- Jason B.
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop--
Wicket 1.2 is coming! Write Ajax applications without touching _javascript_!
-- http://wicketframework.org
