This is one of the classic problems a thin client app has. Stale updates is one of the other.
I solve this via a GUID generator for each transactional screen. The GUID is put in a hidden field and the user's session. The transactional logic in your action=url checks the session for GUID and only forwards the request once to the BL and logs the rest. How's that work for you? curt Tim Endres wrote: >This is usually handled by wrapping JavaScripts around the clickable object >to disable it upon the first click, thus eliminating the next 99 clicks. >tim. > >>Hi, >>If I make 100 clicks fastly from my browser in a servlet, it generates 100 >>requests and 100 processes in the server. One only process is very time >>consuming. >> >>Is there a way to process the fisrt click and avoid the rest 99 clicks. >> >>Any alternatives? >> >>Thank you. >>Andres. >> >> > -- Curt Smith [EMAIL PROTECTED] (h) 404-294-6686 (w) 404-463-0973
