Hey All
I've got a site that has some users who are on very slow connections. These
users have the tendency to click a submit button, wait, click again, wait,
click, click, click - just in case the computer has had trouble
understanding that they clicked the first time.
I am aware that you can do various js work arounds to prevent subsequent
clicks from having any action, but this is kind of messy for all the usual
client side reasons. I am also - wherever possible - checking in my code to
see whether the current action is a duplicate:
query to check if record already exists
if not
do some things
do some more things
do lots more things
write record
However I've still occasionally getting duplicates> I guess they are coming
from the first test being performed on the duplicate before the record is
written for the first item. (home this is making sense)
My question is can you use <cflock type="exclusive"> to lock this code block
and two processes running this same code at the same time? I.e. request 2
waits for request 1 to completely finish before bringing its processing.
I guess I could alternatively put my test immediately before updating the
database:
do some things
do some more things
do lots more things
query to check if record already exists
if not
write record
Thanks in advance
Mark
______________
Mark Stanton
Web Production
Gruden Pty Ltd
Tel: 9956 6388
Mob: 0410 458 201
Fax: 9956 8433
www.gruden.com
---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MX Downunder AsiaPac DevCon - http://mxdu.com/
