This must be a well-known problem: you click multiple times on a form 
button, and multiple requests are send to the server. On many websites they 
ask you not to click on the "confirm purchase" button twice, because 
otherwise you'll be charged twice.

Of course, browsers are to blame for this fault. I can't believe Internet 
Explorer and Netscape are both faulty at this (on Windows platform), but 
that's the sad reality. (What the heck where these programmers thinking when 
they made the form requests non-blocking?!!)

Anyway, how can one handle the problem from the server side? Session 
management is an obvious candidate. Every time you receive a request, you 
set a busy flag, and dump all the following requests, until the first 
request is properly finished. But this has two problems:

(1) You'll see on your browser the response to your last request, not to 
your first request.

(2) If you use RESPONSE.redirect(), your session is locked up.

Of course I can go down into the transaction manager level of Zope and do 
things from there.

But I'd like to know how other people handle the multiple click problem. Is 
there any easy way out?!


Hung Jung

Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com

Zope maillist  -  [EMAIL PROTECTED]
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-dev )

Reply via email to