Why don't you just use a session variable to track if a job was created or not?
User opens a browser, opens a job, gets a job number, gets a session number. User opens another browser, CF sees the session number, and either shows the same job or says "you already have a job open" ______________________ steve oliver atnet solutions, inc. http://www.atnetsolutions.com -----Original Message----- From: Chris Norloff [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 1:39 PM To: CF-Talk Subject: >1 browser window kill client var We just made an interesting discovery. We process multiple jobs, identified by different job numbers. We were looking into using client variables for job numbers, but if (when?) users open more than one browser window this can cause problems. If the user uses a second browser instance to go to another job, then the client vars will be overwritten by the new job number. This is because all the browser instances on a computer look the same to the CFserver - they all have the same CFID/CFTOKEN from that one set of cookies. Anybody find a way to: 1) disable opening new browser windows 2) prevent client var updating if in a different window or something like that? thanks, Chris Norloff ______________________________________________________________________ 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
