RE: 1 browser window kill client var
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/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
Re: 1 browser window kill client var
Use two different browser types: IE Netscape, IE Opera, Netscape Opera Kevin [EMAIL PROTECTED] 02/14/02 10:38AM 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/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
Re: 1 browser window kill client var
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/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
RE: 1 browser window kill client var
Two possible suggestions: Do not allow multiple jobs to be processed simultaneously. That is, do not allow that particular session to process more than one job at a time. The other would be to make arrays of all your job related variables and track them separately. - Original Message - From: Chris Norloff [EMAIL PROTECTED] 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. __ Why Share? Dedicated Win 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=coldfusionc FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
RE: 1 browser window kill client var
Steve Client and Session work the same way, so the problem would still be the same. -Original Message- From: Steve Oliver [mailto:[EMAIL PROTECTED]] Sent: Friday, 15 February 2002 5:47 AM To: CF-Talk Subject: RE: 1 browser window kill client var 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 __ Why Share? Dedicated Win 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=coldfusionc FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
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. -Original Message- From: Steve Oliver [mailto:[EMAIL PROTECTED]] Sent: Friday, 15 February 2002 5:47 AM To: CF-Talk Subject: RE: 1 browser window kill client var 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 __ 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/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
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/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
RE: 1 browser window kill client var
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/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
RE: 1 browser window kill client var
I must be viewing this wrong, here's how I see it. User clicks a button, or clicks a link to create a new job. -Session variable is set saying a job is open. User opens another browser, and clicks the link again to create a new job. -CF sees the existing session variable, and says no, you can't open another job. Are we on different sheets of music or something? __ steve oliver atnet solutions, inc. http://www.atnetsolutions.com -Original Message- From: Steve Oliver [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 11:54 PM To: CF-Talk Subject: RE: 1 browser window kill client var 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/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
RE: 1 browser window kill client var
You can, but the original post was talking about client vars. You suggested using a session var, did you stop to think that session scope is not practical or how about setting a client var. My point is that both session and client work the same, so to the original post you could set either a session or client var to do the check. -Original Message- From: Steve Oliver [mailto:[EMAIL PROTECTED]] Sent: Friday, 15 February 2002 3:54 PM To: CF-Talk Subject: RE: 1 browser window kill client var 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 __ Why Share? Dedicated Win 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=coldfusionc FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
RE: 1 browser window kill client var
Oh, ok, I thought you was saying that it wouldn't work. Yeah if they are using client variables then just set a client variable. My bad. __ steve oliver atnet solutions, inc. http://www.atnetsolutions.com -Original Message- From: Andrew Scott [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 11:58 PM To: CF-Talk Subject: RE: 1 browser window kill client var You can, but the original post was talking about client vars. You suggested using a session var, did you stop to think that session scope is not practical or how about setting a client var. My point is that both session and client work the same, so to the original post you could set either a session or client var to do the check. -Original Message- From: Steve Oliver [mailto:[EMAIL PROTECTED]] Sent: Friday, 15 February 2002 3:54 PM To: CF-Talk Subject: RE: 1 browser window kill client var 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 __ 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/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
