So why can't you check for a session variable on each page load, if it's there don't let them create a new job?
I'm assuming there IS a login to the function that we are talking about, otherwise nevermind. ______________________ steve oliver atnet solutions, inc. http://www.atnetsolutions.com -----Original Message----- From: Andrew Scott [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 11:43 PM To: CF-Talk Subject: RE: >1 browser window kill client var Steve Client and Var scopes work the same way, they are both reliant on the CFID & CFToken. Do I need to spell it out for you. -----Original Message----- From: Steve Oliver [mailto:[EMAIL PROTECTED]] Sent: Friday, 15 February 2002 3:35 PM To: CF-Talk Subject: RE: >1 browser window kill client var I don't see how, if your tracking sessions by cookies, two browsers open will see the same cookie, so you should be able to just check for an existing session variable. ______________________ steve oliver atnet solutions, inc. http://www.atnetsolutions.com -----Original Message----- From: Andrew Scott [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 10:54 PM To: CF-Talk Subject: RE: >1 browser window kill client var Steve Client and Session work the same way, so the problem would still be the same. ______________________________________________________________________ Get Your Own Dedicated Windows 2000 Server PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation � $99/Month � Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusionb FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
