This is why it's a very bad idea to track application state using session or client variables. A user opening two browser windows and performing different tasks in each will usually screw up your logic. You need to know what kind of information you can and cannot safely keep in the client and session scopes. You'll probably end up needing to pass your job number from one page to the next using form or url variables.
Jim ----- Original Message ----- From: "Chris Norloff" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Thursday, February 14, 2002 11:38 AM 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 ______________________________________________________________________ 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=coldfusiona 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
