RE: CFAPPLICATION - Need some advice
Cookies don't get written to the clients cookies.txt file until the browser is closed (they sit in memory until the close). The new cookie, with no expires attribute, never makes it to cookies.txt it just goes away... Matt -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 10, 2000 11:00 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice OK works perfectly but I have one more question to help me understand WHY it's working! I see that when the user closes there browser the cookie gets killed. Then when they revisit the cookie gets re-created by the coldfusion server with new CFID and TOKENs with an expiry time (= session expiry time). Then your bit of code reads from the cookie and overwrites the existing cookie with an immediate expiry. What I'm not sure about is what kills the cookie? I'm assuming that it must be the browser but ow does it know to do it? Does it kill the cookie on closing the browser on when leaving the site?I assume it must be when the browser is closed. A happier but still perplexed Andy! -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 20:29 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice Actually rewriting the cookies turns all cfid/tokens on the client into session cookies (no expires attribute). This doesn't do anything to the server side, where the sessions will eventually die off in memory. this does mess up client variables unfortunately (leaving the cfid/token in your datasource, while killing the cookies on the client). We use only app/session vars, and use a login/database system for client vars so it has not ben an issue. Sorry if this doesn't help you. Matt -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 11:10 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice Okso are you saying that when you re-write the cookie the session/client variables are cleared? If that is the case what happens on the server side? If I am storing client variables in a database o the server and the user closes their browser the record remains in the database. When they re-visit the site the site knows who they are (because of the cookie on their PC) and gives them the same CFID and CFTOKEN. Are you saying that by reassigning these exact same values to the cookies that all of the custom Client variables will get deleted/reset? -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 17:41 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice The code will keep session variables going as long as the browser stays open. It will overwrite the old cfid/token when a new browser window is opened, the result is your old session variables are killed and you start over. -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 10:02 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice I don't think this will do what we are hoping it will. It looks to me as if all it's doing is testing to see if the session is open, if it is it's reading the values from the cookies and then putting them back in there.am I completely off the mark here?? -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 16:27 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice Put this code in your application.cfm file. It will kill the session variables when the user closes the browser: -Original Message- From: Miguel [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 9:08 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice There's none, either in asp nor php4 Javascript is the way Miguel Gonzalez www.ibcmass.com mailto:[EMAIL PROTECTED] > -Mensaje original- > De: Andy Ewings [mailto:[EMAIL PROTECTED]] > Enviado el: miércoles 9 de agosto de 2000 14:52 > Para: '[EMAIL PROTECTED]' > Asunto: RE: CFAPPLICATION - Need some advice > > > Session management is a bit of a nightmare in CF in my > opinion. If the user > closes their browser their session doesn't expire > automatically. One only > way to force it to expire is to use the 'OnUnload' event of > the browser to > trigger some Java Script which ends the session. > > If anyone else has any other ideas on this I'd love to hear them. > > > -Original Message- > From: Gavin Myers [mailto:[EMAIL PROTECTED]] > Sent: 09 August 2000 13:41 > To: '[EMAIL PROTECTED]' > Subject: CFAPPLICATION - Need some advice > > > I've decided to take a look at application.cfm too see what I > can
RE: CFAPPLICATION - Need some advice
Its just that client vars are generally a longer term storage type of item. Andy's app uses them like session vars which are very short term. The administrator defaults to a purge after 90 days of no visits, even 1 day would be too much for this situation. So it makes sense to make an effort to clean up old client vars. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 10, 2000 10:37 AM To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice Curious - in what way does this mess up client vars in a database? Doesn't CF remove abandoned client vars cleanly? -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 10, 2000 12:02 PM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice Superstar.that worked a treat.you don't know how long I've been looking at this!! -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 20:29 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice Actually rewriting the cookies turns all cfid/tokens on the client into session cookies (no expires attribute). This doesn't do anything to the server side, where the sessions will eventually die off in memory. this does mess up client variables unfortunately (leaving the cfid/token in your datasource, while killing the cookies on the client). We use only app/session vars, and use a login/database system for client vars so it has not ben an issue. Sorry if this doesn't help you. Matt -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 11:10 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice Okso are you saying that when you re-write the cookie the session/client variables are cleared? If that is the case what happens on the server side? If I am storing client variables in a database o the server and the user closes their browser the record remains in the database. When they re-visit the site the site knows who they are (because of the cookie on their PC) and gives them the same CFID and CFTOKEN. Are you saying that by reassigning these exact same values to the cookies that all of the custom Client variables will get deleted/reset? -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 17:41 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice The code will keep session variables going as long as the browser stays open. It will overwrite the old cfid/token when a new browser window is opened, the result is your old session variables are killed and you start over. -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 10:02 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice I don't think this will do what we are hoping it will. It looks to me as if all it's doing is testing to see if the session is open, if it is it's reading the values from the cookies and then putting them back in there.am I completely off the mark here?? -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 16:27 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice Put this code in your application.cfm file. It will kill the session variables when the user closes the browser: -Original Message- From: Miguel [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 9:08 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice There's none, either in asp nor php4 Javascript is the way Miguel Gonzalez www.ibcmass.com mailto:[EMAIL PROTECTED] > -Mensaje original- > De: Andy Ewings [mailto:[EMAIL PROTECTED]] > Enviado el: miércoles 9 de agosto de 2000 14:52 > Para: '[EMAIL PROTECTED]' > Asunto: RE: CFAPPLICATION - Need some advice > > > Session management is a bit of a nightmare in CF in my > opinion. If the user > closes their browser their session doesn't expire > automatically. One only > way to force it to expire is to use the 'OnUnload' event of > the browser to > trigger some Java Script which ends the session. > > If anyone else has any other ideas on this I'd love to hear them. > > > -Original Message- > From: Gavin Myers [mailto:[EMAIL PROTECTED]] > Sent: 09 August 2000 13:41 > To: '[EMAIL PROTECTED]' > Subject: CFAPPLICATION - Need some advice > > > I've decided to take a look at application.cfm too see what I > can gather. > I've never really used it before > > Now in the simplest form: > > application.cfm > > > sessionmanagement="Yes" > setclientcookies="Yes"> >
RE: CFAPPLICATION - Need some advice
OK works perfectly but I have one more question to help me understand WHY it's working! I see that when the user closes there browser the cookie gets killed. Then when they revisit the cookie gets re-created by the coldfusion server with new CFID and TOKENs with an expiry time (= session expiry time). Then your bit of code reads from the cookie and overwrites the existing cookie with an immediate expiry. What I'm not sure about is what kills the cookie? I'm assuming that it must be the browser but ow does it know to do it? Does it kill the cookie on closing the browser on when leaving the site?I assume it must be when the browser is closed. A happier but still perplexed Andy! -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 20:29 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice Actually rewriting the cookies turns all cfid/tokens on the client into session cookies (no expires attribute). This doesn't do anything to the server side, where the sessions will eventually die off in memory. this does mess up client variables unfortunately (leaving the cfid/token in your datasource, while killing the cookies on the client). We use only app/session vars, and use a login/database system for client vars so it has not ben an issue. Sorry if this doesn't help you. Matt -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 11:10 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice Okso are you saying that when you re-write the cookie the session/client variables are cleared? If that is the case what happens on the server side? If I am storing client variables in a database o the server and the user closes their browser the record remains in the database. When they re-visit the site the site knows who they are (because of the cookie on their PC) and gives them the same CFID and CFTOKEN. Are you saying that by reassigning these exact same values to the cookies that all of the custom Client variables will get deleted/reset? -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 17:41 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice The code will keep session variables going as long as the browser stays open. It will overwrite the old cfid/token when a new browser window is opened, the result is your old session variables are killed and you start over. -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 10:02 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice I don't think this will do what we are hoping it will. It looks to me as if all it's doing is testing to see if the session is open, if it is it's reading the values from the cookies and then putting them back in there.am I completely off the mark here?? -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 16:27 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice Put this code in your application.cfm file. It will kill the session variables when the user closes the browser: -Original Message- From: Miguel [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 9:08 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice There's none, either in asp nor php4 Javascript is the way Miguel Gonzalez www.ibcmass.com mailto:[EMAIL PROTECTED] > -Mensaje original- > De: Andy Ewings [mailto:[EMAIL PROTECTED]] > Enviado el: miércoles 9 de agosto de 2000 14:52 > Para: '[EMAIL PROTECTED]' > Asunto: RE: CFAPPLICATION - Need some advice > > > Session management is a bit of a nightmare in CF in my > opinion. If the user > closes their browser their session doesn't expire > automatically. One only > way to force it to expire is to use the 'OnUnload' event of > the browser to > trigger some Java Script which ends the session. > > If anyone else has any other ideas on this I'd love to hear them. > > > -Original Message- > From: Gavin Myers [mailto:[EMAIL PROTECTED]] > Sent: 09 August 2000 13:41 > To: '[EMAIL PROTECTED]' > Subject: CFAPPLICATION - Need some advice > > > I've decided to take a look at application.cfm too see what I > can gather. > I've never really used it before > > Now in the simplest form: > > application.cfm > > > sessionmanagement="Yes" > setclientcookies="Yes"> > > > end application.cfm > > The only thing I am using with the application.cfm file is > #session.sessionid#, and I need to carry that sessionid > through pages. But, > I also want to make it so that w
RE: CFAPPLICATION - Need some advice
Curious - in what way does this mess up client vars in a database? Doesn't CF remove abandoned client vars cleanly? -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 10, 2000 12:02 PM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice Superstar.that worked a treat.you don't know how long I've been looking at this!! -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 20:29 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice Actually rewriting the cookies turns all cfid/tokens on the client into session cookies (no expires attribute). This doesn't do anything to the server side, where the sessions will eventually die off in memory. this does mess up client variables unfortunately (leaving the cfid/token in your datasource, while killing the cookies on the client). We use only app/session vars, and use a login/database system for client vars so it has not ben an issue. Sorry if this doesn't help you. Matt -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 11:10 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice Okso are you saying that when you re-write the cookie the session/client variables are cleared? If that is the case what happens on the server side? If I am storing client variables in a database o the server and the user closes their browser the record remains in the database. When they re-visit the site the site knows who they are (because of the cookie on their PC) and gives them the same CFID and CFTOKEN. Are you saying that by reassigning these exact same values to the cookies that all of the custom Client variables will get deleted/reset? -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 17:41 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice The code will keep session variables going as long as the browser stays open. It will overwrite the old cfid/token when a new browser window is opened, the result is your old session variables are killed and you start over. -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 10:02 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice I don't think this will do what we are hoping it will. It looks to me as if all it's doing is testing to see if the session is open, if it is it's reading the values from the cookies and then putting them back in there.am I completely off the mark here?? -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 16:27 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice Put this code in your application.cfm file. It will kill the session variables when the user closes the browser: -Original Message- From: Miguel [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 9:08 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice There's none, either in asp nor php4 Javascript is the way Miguel Gonzalez www.ibcmass.com mailto:[EMAIL PROTECTED] > -Mensaje original- > De: Andy Ewings [mailto:[EMAIL PROTECTED]] > Enviado el: miércoles 9 de agosto de 2000 14:52 > Para: '[EMAIL PROTECTED]' > Asunto: RE: CFAPPLICATION - Need some advice > > > Session management is a bit of a nightmare in CF in my > opinion. If the user > closes their browser their session doesn't expire > automatically. One only > way to force it to expire is to use the 'OnUnload' event of > the browser to > trigger some Java Script which ends the session. > > If anyone else has any other ideas on this I'd love to hear them. > > > -Original Message- > From: Gavin Myers [mailto:[EMAIL PROTECTED]] > Sent: 09 August 2000 13:41 > To: '[EMAIL PROTECTED]' > Subject: CFAPPLICATION - Need some advice > > > I've decided to take a look at application.cfm too see what I > can gather. > I've never really used it before > > Now in the simplest form: > > application.cfm > > > sessionmanagement="Yes" > setclientcookies="Yes"> > > > end application.cfm > > The only thing I am using with the application.cfm file is > #session.sessionid#, and I need to carry that sessionid > through pages. But, > I also want to make it so that when a person leaves my site, > and then goes > back they don't get the same sessionid, but a brand new one. > I could set an > expire date, but I'd rather have it not use the same one over again > automatically. Any suggestions? > > Oh and while were on the s
RE: CFAPPLICATION - Need some advice
Superstar.that worked a treat.you don't know how long I've been looking at this!! -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 20:29 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice Actually rewriting the cookies turns all cfid/tokens on the client into session cookies (no expires attribute). This doesn't do anything to the server side, where the sessions will eventually die off in memory. this does mess up client variables unfortunately (leaving the cfid/token in your datasource, while killing the cookies on the client). We use only app/session vars, and use a login/database system for client vars so it has not ben an issue. Sorry if this doesn't help you. Matt -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 11:10 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice Okso are you saying that when you re-write the cookie the session/client variables are cleared? If that is the case what happens on the server side? If I am storing client variables in a database o the server and the user closes their browser the record remains in the database. When they re-visit the site the site knows who they are (because of the cookie on their PC) and gives them the same CFID and CFTOKEN. Are you saying that by reassigning these exact same values to the cookies that all of the custom Client variables will get deleted/reset? -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 17:41 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice The code will keep session variables going as long as the browser stays open. It will overwrite the old cfid/token when a new browser window is opened, the result is your old session variables are killed and you start over. -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 10:02 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice I don't think this will do what we are hoping it will. It looks to me as if all it's doing is testing to see if the session is open, if it is it's reading the values from the cookies and then putting them back in there.am I completely off the mark here?? -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 16:27 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice Put this code in your application.cfm file. It will kill the session variables when the user closes the browser: -Original Message- From: Miguel [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 9:08 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice There's none, either in asp nor php4 Javascript is the way Miguel Gonzalez www.ibcmass.com mailto:[EMAIL PROTECTED] > -Mensaje original- > De: Andy Ewings [mailto:[EMAIL PROTECTED]] > Enviado el: miércoles 9 de agosto de 2000 14:52 > Para: '[EMAIL PROTECTED]' > Asunto: RE: CFAPPLICATION - Need some advice > > > Session management is a bit of a nightmare in CF in my > opinion. If the user > closes their browser their session doesn't expire > automatically. One only > way to force it to expire is to use the 'OnUnload' event of > the browser to > trigger some Java Script which ends the session. > > If anyone else has any other ideas on this I'd love to hear them. > > > -Original Message- > From: Gavin Myers [mailto:[EMAIL PROTECTED]] > Sent: 09 August 2000 13:41 > To: '[EMAIL PROTECTED]' > Subject: CFAPPLICATION - Need some advice > > > I've decided to take a look at application.cfm too see what I > can gather. > I've never really used it before > > Now in the simplest form: > > application.cfm > > > sessionmanagement="Yes" > setclientcookies="Yes"> > > > end application.cfm > > The only thing I am using with the application.cfm file is > #session.sessionid#, and I need to carry that sessionid > through pages. But, > I also want to make it so that when a person leaves my site, > and then goes > back they don't get the same sessionid, but a brand new one. > I could set an > expire date, but I'd rather have it not use the same one over again > automatically. Any suggestions? > > Oh and while were on the subject, I want to set global variables while > person-x is in the site. Example: > > Making a shopping cart that records when a person checks on a > radio button > labled purchase. That way when they are 4-99 pages deep they > can hit buy and > bring up a list of all of the things they said
RE: CFAPPLICATION - Need some advice
Thanks...I'll try it and let you know how I get on.. -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 10 August 2000 15:57 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice Yes, setting the cookie without an expires attribute makes a cookie that will expire when the browser closes. All you are doing is replacing a persistent cookie with a session cookie. When the user closes their browser the cookie will die and they won't be logged in if they reopen the page. Your client variable data will build up but scheduling a purge of old data should be easy enough. Matt -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 10, 2000 5:10 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice Let me see if I understand you correctly..if you create your own cookies to store CFID and TOKEN, overwriting the ones put there by default by CF, do these cookies automatically get destroyed when the browser is closed as opposed to the default cookies which expire on the client when the session expires? The reason I am trying to do this is because I have a large site, split over three servers (2 web and a database) and I am setting them up so they are load balanced (so using Client variables instead of session variables). The site is driven by a single page that pulls in other pages and at the top of this page there is a test to ensure the user has logged in. I want to force the site to log the user out when they close their browser. If this code does what I think your saying it does then I think it'll workthe only problem I'll have is a build up of client variable data in the database but I guess I can get CF to purge this on a regular basis. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 23:39 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice > > Put this code in your application.cfm file. It will kill the session > > variables when the user closes the browser: > > > > > > > > > > > > > > > > ... > I don't think this will do what we are hoping it will. It looks to > me as if all it's doing is testing to see if the session is open, > if it is it's reading the values from the cookies and then putting > them back in there.am I completely off the mark here?? The above code is overwriting the cookies that CF automatically creates, which are persistent beyond the life of the browser instance, with cookies that will be destroyed when the browser is closed. Thus, when a user closes the browser, they destroy their link to the session variables on the server, effectively ending their session. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
RE: CFAPPLICATION - Need some advice
Yes, setting the cookie without an expires attribute makes a cookie that will expire when the browser closes. All you are doing is replacing a persistent cookie with a session cookie. When the user closes their browser the cookie will die and they won't be logged in if they reopen the page. Your client variable data will build up but scheduling a purge of old data should be easy enough. Matt -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 10, 2000 5:10 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice Let me see if I understand you correctly..if you create your own cookies to store CFID and TOKEN, overwriting the ones put there by default by CF, do these cookies automatically get destroyed when the browser is closed as opposed to the default cookies which expire on the client when the session expires? The reason I am trying to do this is because I have a large site, split over three servers (2 web and a database) and I am setting them up so they are load balanced (so using Client variables instead of session variables). The site is driven by a single page that pulls in other pages and at the top of this page there is a test to ensure the user has logged in. I want to force the site to log the user out when they close their browser. If this code does what I think your saying it does then I think it'll workthe only problem I'll have is a build up of client variable data in the database but I guess I can get CF to purge this on a regular basis. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 23:39 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice > > Put this code in your application.cfm file. It will kill the session > > variables when the user closes the browser: > > > > > > > > > > > > > > > > ... > I don't think this will do what we are hoping it will. It looks to > me as if all it's doing is testing to see if the session is open, > if it is it's reading the values from the cookies and then putting > them back in there.am I completely off the mark here?? The above code is overwriting the cookies that CF automatically creates, which are persistent beyond the life of the browser instance, with cookies that will be destroyed when the browser is closed. Thus, when a user closes the browser, they destroy their link to the session variables on the server, effectively ending their session. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
RE: CFAPPLICATION - Need some advice
Let me see if I understand you correctly..if you create your own cookies to store CFID and TOKEN, overwriting the ones put there by default by CF, do these cookies automatically get destroyed when the browser is closed as opposed to the default cookies which expire on the client when the session expires? The reason I am trying to do this is because I have a large site, split over three servers (2 web and a database) and I am setting them up so they are load balanced (so using Client variables instead of session variables). The site is driven by a single page that pulls in other pages and at the top of this page there is a test to ensure the user has logged in. I want to force the site to log the user out when they close their browser. If this code does what I think your saying it does then I think it'll workthe only problem I'll have is a build up of client variable data in the database but I guess I can get CF to purge this on a regular basis. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 23:39 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice > > Put this code in your application.cfm file. It will kill the session > > variables when the user closes the browser: > > > > > > > > > > > > > > > > ... > I don't think this will do what we are hoping it will. It looks to > me as if all it's doing is testing to see if the session is open, > if it is it's reading the values from the cookies and then putting > them back in there.am I completely off the mark here?? The above code is overwriting the cookies that CF automatically creates, which are persistent beyond the life of the browser instance, with cookies that will be destroyed when the browser is closed. Thus, when a user closes the browser, they destroy their link to the session variables on the server, effectively ending their session. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
RE: CFAPPLICATION - Need some advice
Thank you for that clear explanation. I was scratching my head at this code... :-) At 06:38 PM 8/9/00 -0400, Dave Watts wrote: >> > Put this code in your application.cfm file. It will kill the session >> > variables when the user closes the browser: >> > >> > >> > >> > >> > >> > >> > >> > >... >> I don't think this will do what we are hoping it will. It looks to >> me as if all it's doing is testing to see if the session is open, >> if it is it's reading the values from the cookies and then putting >> them back in there.am I completely off the mark here?? > >The above code is overwriting the cookies that CF automatically creates, >which are persistent beyond the life of the browser instance, with cookies >that will be destroyed when the browser is closed. Thus, when a user closes >the browser, they destroy their link to the session variables on the server, >effectively ending their session. > >Dave Watts, CTO, Fig Leaf Software >http://www.figleaf.com/ >voice: (202) 797-5496 >fax: (202) 797-5444 > >-- >Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ >To Unsubscribe visit >http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a >message to [EMAIL PROTECTED] with 'unsubscribe' in the body. --- Peter Theobald, Chief Technology Officer LiquidStreaming http://www.liquidstreaming.com [EMAIL PROTECTED] Phone 1.212.545.1232 Fax 1.212.679.8032 -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
RE: CFAPPLICATION - Need some advice
> > Put this code in your application.cfm file. It will kill the session > > variables when the user closes the browser: > > > > > > > > > > > > > > > > ... > I don't think this will do what we are hoping it will. It looks to > me as if all it's doing is testing to see if the session is open, > if it is it's reading the values from the cookies and then putting > them back in there.am I completely off the mark here?? The above code is overwriting the cookies that CF automatically creates, which are persistent beyond the life of the browser instance, with cookies that will be destroyed when the browser is closed. Thus, when a user closes the browser, they destroy their link to the session variables on the server, effectively ending their session. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
RE: CFAPPLICATION - Need some advice
Actually rewriting the cookies turns all cfid/tokens on the client into session cookies (no expires attribute). This doesn't do anything to the server side, where the sessions will eventually die off in memory. this does mess up client variables unfortunately (leaving the cfid/token in your datasource, while killing the cookies on the client). We use only app/session vars, and use a login/database system for client vars so it has not ben an issue. Sorry if this doesn't help you. Matt -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 11:10 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice Okso are you saying that when you re-write the cookie the session/client variables are cleared? If that is the case what happens on the server side? If I am storing client variables in a database o the server and the user closes their browser the record remains in the database. When they re-visit the site the site knows who they are (because of the cookie on their PC) and gives them the same CFID and CFTOKEN. Are you saying that by reassigning these exact same values to the cookies that all of the custom Client variables will get deleted/reset? -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 17:41 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice The code will keep session variables going as long as the browser stays open. It will overwrite the old cfid/token when a new browser window is opened, the result is your old session variables are killed and you start over. -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 10:02 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice I don't think this will do what we are hoping it will. It looks to me as if all it's doing is testing to see if the session is open, if it is it's reading the values from the cookies and then putting them back in there.am I completely off the mark here?? -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 16:27 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice Put this code in your application.cfm file. It will kill the session variables when the user closes the browser: -Original Message- From: Miguel [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 9:08 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice There's none, either in asp nor php4 Javascript is the way Miguel Gonzalez www.ibcmass.com mailto:[EMAIL PROTECTED] > -Mensaje original- > De: Andy Ewings [mailto:[EMAIL PROTECTED]] > Enviado el: miércoles 9 de agosto de 2000 14:52 > Para: '[EMAIL PROTECTED]' > Asunto: RE: CFAPPLICATION - Need some advice > > > Session management is a bit of a nightmare in CF in my > opinion. If the user > closes their browser their session doesn't expire > automatically. One only > way to force it to expire is to use the 'OnUnload' event of > the browser to > trigger some Java Script which ends the session. > > If anyone else has any other ideas on this I'd love to hear them. > > > -Original Message- > From: Gavin Myers [mailto:[EMAIL PROTECTED]] > Sent: 09 August 2000 13:41 > To: '[EMAIL PROTECTED]' > Subject: CFAPPLICATION - Need some advice > > > I've decided to take a look at application.cfm too see what I > can gather. > I've never really used it before > > Now in the simplest form: > > application.cfm > > > sessionmanagement="Yes" > setclientcookies="Yes"> > > > end application.cfm > > The only thing I am using with the application.cfm file is > #session.sessionid#, and I need to carry that sessionid > through pages. But, > I also want to make it so that when a person leaves my site, > and then goes > back they don't get the same sessionid, but a brand new one. > I could set an > expire date, but I'd rather have it not use the same one over again > automatically. Any suggestions? > > Oh and while were on the subject, I want to set global variables while > person-x is in the site. Example: > > Making a shopping cart that records when a person checks on a > radio button > labled purchase. That way when they are 4-99 pages deep they > can hit buy and > bring up a list of all of the things they said yes to. So you > click on yes, > and it globals the name of the product and the product_id, so I can > reference it later. > > Thanks, > Gavin > -- > -- > -- > Archives: ht
RE: CFAPPLICATION - Need some advice
Okso are you saying that when you re-write the cookie the session/client variables are cleared? If that is the case what happens on the server side? If I am storing client variables in a database o the server and the user closes their browser the record remains in the database. When they re-visit the site the site knows who they are (because of the cookie on their PC) and gives them the same CFID and CFTOKEN. Are you saying that by reassigning these exact same values to the cookies that all of the custom Client variables will get deleted/reset? -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 17:41 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice The code will keep session variables going as long as the browser stays open. It will overwrite the old cfid/token when a new browser window is opened, the result is your old session variables are killed and you start over. -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 10:02 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice I don't think this will do what we are hoping it will. It looks to me as if all it's doing is testing to see if the session is open, if it is it's reading the values from the cookies and then putting them back in there.am I completely off the mark here?? -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 16:27 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice Put this code in your application.cfm file. It will kill the session variables when the user closes the browser: -Original Message- From: Miguel [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 9:08 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice There's none, either in asp nor php4 Javascript is the way Miguel Gonzalez www.ibcmass.com mailto:[EMAIL PROTECTED] > -Mensaje original- > De: Andy Ewings [mailto:[EMAIL PROTECTED]] > Enviado el: miércoles 9 de agosto de 2000 14:52 > Para: '[EMAIL PROTECTED]' > Asunto: RE: CFAPPLICATION - Need some advice > > > Session management is a bit of a nightmare in CF in my > opinion. If the user > closes their browser their session doesn't expire > automatically. One only > way to force it to expire is to use the 'OnUnload' event of > the browser to > trigger some Java Script which ends the session. > > If anyone else has any other ideas on this I'd love to hear them. > > > -Original Message- > From: Gavin Myers [mailto:[EMAIL PROTECTED]] > Sent: 09 August 2000 13:41 > To: '[EMAIL PROTECTED]' > Subject: CFAPPLICATION - Need some advice > > > I've decided to take a look at application.cfm too see what I > can gather. > I've never really used it before > > Now in the simplest form: > > application.cfm > > > sessionmanagement="Yes" > setclientcookies="Yes"> > > > end application.cfm > > The only thing I am using with the application.cfm file is > #session.sessionid#, and I need to carry that sessionid > through pages. But, > I also want to make it so that when a person leaves my site, > and then goes > back they don't get the same sessionid, but a brand new one. > I could set an > expire date, but I'd rather have it not use the same one over again > automatically. Any suggestions? > > Oh and while were on the subject, I want to set global variables while > person-x is in the site. Example: > > Making a shopping cart that records when a person checks on a > radio button > labled purchase. That way when they are 4-99 pages deep they > can hit buy and > bring up a list of all of the things they said yes to. So you > click on yes, > and it globals the name of the product and the product_id, so I can > reference it later. > > Thanks, > Gavin > -- > -- > -- > Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ > To Unsubscribe visit > http://www.houseoffusion.com/index.cfm?sidebar=lists&body=list s/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion
RE: CFAPPLICATION - Need some advice
Ok well that would explain why a site with frames wouldn't work right. Is there anyway I can stop this from happening? Maybe putting a lock around the cfapplication? Something, anything. Robert Everland III Web Developer Dixon Ticonderoga -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 12:41 PM To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice The code will keep session variables going as long as the browser stays open. It will overwrite the old cfid/token when a new browser window is opened, the result is your old session variables are killed and you start over. -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 10:02 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice I don't think this will do what we are hoping it will. It looks to me as if all it's doing is testing to see if the session is open, if it is it's reading the values from the cookies and then putting them back in there.am I completely off the mark here?? -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 16:27 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice Put this code in your application.cfm file. It will kill the session variables when the user closes the browser: -Original Message- From: Miguel [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 9:08 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice There's none, either in asp nor php4 Javascript is the way Miguel Gonzalez www.ibcmass.com mailto:[EMAIL PROTECTED] > -Mensaje original- > De: Andy Ewings [mailto:[EMAIL PROTECTED]] > Enviado el: miércoles 9 de agosto de 2000 14:52 > Para: '[EMAIL PROTECTED]' > Asunto: RE: CFAPPLICATION - Need some advice > > > Session management is a bit of a nightmare in CF in my > opinion. If the user > closes their browser their session doesn't expire > automatically. One only > way to force it to expire is to use the 'OnUnload' event of > the browser to > trigger some Java Script which ends the session. > > If anyone else has any other ideas on this I'd love to hear them. > > > -Original Message- > From: Gavin Myers [mailto:[EMAIL PROTECTED]] > Sent: 09 August 2000 13:41 > To: '[EMAIL PROTECTED]' > Subject: CFAPPLICATION - Need some advice > > > I've decided to take a look at application.cfm too see what I > can gather. > I've never really used it before > > Now in the simplest form: > > application.cfm > > > sessionmanagement="Yes" > setclientcookies="Yes"> > > > end application.cfm > > The only thing I am using with the application.cfm file is > #session.sessionid#, and I need to carry that sessionid > through pages. But, > I also want to make it so that when a person leaves my site, > and then goes > back they don't get the same sessionid, but a brand new one. > I could set an > expire date, but I'd rather have it not use the same one over again > automatically. Any suggestions? > > Oh and while were on the subject, I want to set global variables while > person-x is in the site. Example: > > Making a shopping cart that records when a person checks on a > radio button > labled purchase. That way when they are 4-99 pages deep they > can hit buy and > bring up a list of all of the things they said yes to. So you > click on yes, > and it globals the name of the product and the product_id, so I can > reference it later. > > Thanks, > Gavin > -- > -- > -- > Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ > To Unsubscribe visit > http://www.houseoffusion.com/index.cfm?sidebar=lists&body=list s/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=sts&body=sts/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://ww
RE: CFAPPLICATION - Need some advice
The code will keep session variables going as long as the browser stays open. It will overwrite the old cfid/token when a new browser window is opened, the result is your old session variables are killed and you start over. -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 10:02 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice I don't think this will do what we are hoping it will. It looks to me as if all it's doing is testing to see if the session is open, if it is it's reading the values from the cookies and then putting them back in there.am I completely off the mark here?? -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 16:27 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice Put this code in your application.cfm file. It will kill the session variables when the user closes the browser: -Original Message- From: Miguel [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 9:08 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice There's none, either in asp nor php4 Javascript is the way Miguel Gonzalez www.ibcmass.com mailto:[EMAIL PROTECTED] > -Mensaje original- > De: Andy Ewings [mailto:[EMAIL PROTECTED]] > Enviado el: miércoles 9 de agosto de 2000 14:52 > Para: '[EMAIL PROTECTED]' > Asunto: RE: CFAPPLICATION - Need some advice > > > Session management is a bit of a nightmare in CF in my > opinion. If the user > closes their browser their session doesn't expire > automatically. One only > way to force it to expire is to use the 'OnUnload' event of > the browser to > trigger some Java Script which ends the session. > > If anyone else has any other ideas on this I'd love to hear them. > > > -Original Message- > From: Gavin Myers [mailto:[EMAIL PROTECTED]] > Sent: 09 August 2000 13:41 > To: '[EMAIL PROTECTED]' > Subject: CFAPPLICATION - Need some advice > > > I've decided to take a look at application.cfm too see what I > can gather. > I've never really used it before > > Now in the simplest form: > > application.cfm > > > sessionmanagement="Yes" > setclientcookies="Yes"> > > > end application.cfm > > The only thing I am using with the application.cfm file is > #session.sessionid#, and I need to carry that sessionid > through pages. But, > I also want to make it so that when a person leaves my site, > and then goes > back they don't get the same sessionid, but a brand new one. > I could set an > expire date, but I'd rather have it not use the same one over again > automatically. Any suggestions? > > Oh and while were on the subject, I want to set global variables while > person-x is in the site. Example: > > Making a shopping cart that records when a person checks on a > radio button > labled purchase. That way when they are 4-99 pages deep they > can hit buy and > bring up a list of all of the things they said yes to. So you > click on yes, > and it globals the name of the product and the product_id, so I can > reference it later. > > Thanks, > Gavin > -- > -- > -- > Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ > To Unsubscribe visit > http://www.houseoffusion.com/index.cfm?sidebar=lists&body=list s/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=sts&body=sts/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=sts&body=sts/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
RE: CFAPPLICATION - Need some advice
I don't think this will do what we are hoping it will. It looks to me as if all it's doing is testing to see if the session is open, if it is it's reading the values from the cookies and then putting them back in there.am I completely off the mark here?? -Original Message- From: Matt Rodosky [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 16:27 To: [EMAIL PROTECTED] Subject: RE: CFAPPLICATION - Need some advice Put this code in your application.cfm file. It will kill the session variables when the user closes the browser: -Original Message- From: Miguel [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 9:08 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice There's none, either in asp nor php4 Javascript is the way Miguel Gonzalez www.ibcmass.com mailto:[EMAIL PROTECTED] > -Mensaje original- > De: Andy Ewings [mailto:[EMAIL PROTECTED]] > Enviado el: miércoles 9 de agosto de 2000 14:52 > Para: '[EMAIL PROTECTED]' > Asunto: RE: CFAPPLICATION - Need some advice > > > Session management is a bit of a nightmare in CF in my > opinion. If the user > closes their browser their session doesn't expire > automatically. One only > way to force it to expire is to use the 'OnUnload' event of > the browser to > trigger some Java Script which ends the session. > > If anyone else has any other ideas on this I'd love to hear them. > > > -Original Message- > From: Gavin Myers [mailto:[EMAIL PROTECTED]] > Sent: 09 August 2000 13:41 > To: '[EMAIL PROTECTED]' > Subject: CFAPPLICATION - Need some advice > > > I've decided to take a look at application.cfm too see what I > can gather. > I've never really used it before > > Now in the simplest form: > > application.cfm > > > sessionmanagement="Yes" > setclientcookies="Yes"> > > > end application.cfm > > The only thing I am using with the application.cfm file is > #session.sessionid#, and I need to carry that sessionid > through pages. But, > I also want to make it so that when a person leaves my site, > and then goes > back they don't get the same sessionid, but a brand new one. > I could set an > expire date, but I'd rather have it not use the same one over again > automatically. Any suggestions? > > Oh and while were on the subject, I want to set global variables while > person-x is in the site. Example: > > Making a shopping cart that records when a person checks on a > radio button > labled purchase. That way when they are 4-99 pages deep they > can hit buy and > bring up a list of all of the things they said yes to. So you > click on yes, > and it globals the name of the product and the product_id, so I can > reference it later. > > Thanks, > Gavin > -- > -- > -- > Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ > To Unsubscribe visit > http://www.houseoffusion.com/index.cfm?sidebar=lists&body=list s/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=sts&body=sts/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebarRsts&bodyRsts/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
RE: CFAPPLICATION - Need some advice
Put this code in your application.cfm file. It will kill the session variables when the user closes the browser: -Original Message- From: Miguel [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 9:08 AM To: '[EMAIL PROTECTED]' Subject: RE: CFAPPLICATION - Need some advice There's none, either in asp nor php4 Javascript is the way Miguel Gonzalez www.ibcmass.com mailto:[EMAIL PROTECTED] > -Mensaje original- > De: Andy Ewings [mailto:[EMAIL PROTECTED]] > Enviado el: miércoles 9 de agosto de 2000 14:52 > Para: '[EMAIL PROTECTED]' > Asunto: RE: CFAPPLICATION - Need some advice > > > Session management is a bit of a nightmare in CF in my > opinion. If the user > closes their browser their session doesn't expire > automatically. One only > way to force it to expire is to use the 'OnUnload' event of > the browser to > trigger some Java Script which ends the session. > > If anyone else has any other ideas on this I'd love to hear them. > > > -Original Message- > From: Gavin Myers [mailto:[EMAIL PROTECTED]] > Sent: 09 August 2000 13:41 > To: '[EMAIL PROTECTED]' > Subject: CFAPPLICATION - Need some advice > > > I've decided to take a look at application.cfm too see what I > can gather. > I've never really used it before > > Now in the simplest form: > > application.cfm > > > sessionmanagement="Yes" > setclientcookies="Yes"> > > > end application.cfm > > The only thing I am using with the application.cfm file is > #session.sessionid#, and I need to carry that sessionid > through pages. But, > I also want to make it so that when a person leaves my site, > and then goes > back they don't get the same sessionid, but a brand new one. > I could set an > expire date, but I'd rather have it not use the same one over again > automatically. Any suggestions? > > Oh and while were on the subject, I want to set global variables while > person-x is in the site. Example: > > Making a shopping cart that records when a person checks on a > radio button > labled purchase. That way when they are 4-99 pages deep they > can hit buy and > bring up a list of all of the things they said yes to. So you > click on yes, > and it globals the name of the product and the product_id, so I can > reference it later. > > Thanks, > Gavin > -- > -- > -- > Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ > To Unsubscribe visit > http://www.houseoffusion.com/index.cfm?sidebar=lists&body=list s/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=sts&body=sts/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
RE: CFAPPLICATION - Need some advice
There's none, either in asp nor php4 Javascript is the way Miguel Gonzalez www.ibcmass.com mailto:[EMAIL PROTECTED] > -Mensaje original- > De: Andy Ewings [mailto:[EMAIL PROTECTED]] > Enviado el: miércoles 9 de agosto de 2000 14:52 > Para: '[EMAIL PROTECTED]' > Asunto: RE: CFAPPLICATION - Need some advice > > > Session management is a bit of a nightmare in CF in my > opinion. If the user > closes their browser their session doesn't expire > automatically. One only > way to force it to expire is to use the 'OnUnload' event of > the browser to > trigger some Java Script which ends the session. > > If anyone else has any other ideas on this I'd love to hear them. > > > -Original Message- > From: Gavin Myers [mailto:[EMAIL PROTECTED]] > Sent: 09 August 2000 13:41 > To: '[EMAIL PROTECTED]' > Subject: CFAPPLICATION - Need some advice > > > I've decided to take a look at application.cfm too see what I > can gather. > I've never really used it before > > Now in the simplest form: > > application.cfm > > > sessionmanagement="Yes" > setclientcookies="Yes"> > > > end application.cfm > > The only thing I am using with the application.cfm file is > #session.sessionid#, and I need to carry that sessionid > through pages. But, > I also want to make it so that when a person leaves my site, > and then goes > back they don't get the same sessionid, but a brand new one. > I could set an > expire date, but I'd rather have it not use the same one over again > automatically. Any suggestions? > > Oh and while were on the subject, I want to set global variables while > person-x is in the site. Example: > > Making a shopping cart that records when a person checks on a > radio button > labled purchase. That way when they are 4-99 pages deep they > can hit buy and > bring up a list of all of the things they said yes to. So you > click on yes, > and it globals the name of the product and the product_id, so I can > reference it later. > > Thanks, > Gavin > -- > -- > -- > Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ > To Unsubscribe visit > http://www.houseoffusion.com/index.cfm?sidebar=lists&body=list s/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebarRsts&bodyRsts/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
RE: CFAPPLICATION - Need some advice
Session management is a bit of a nightmare in CF in my opinion. If the user closes their browser their session doesn't expire automatically. One only way to force it to expire is to use the 'OnUnload' event of the browser to trigger some Java Script which ends the session. If anyone else has any other ideas on this I'd love to hear them. -Original Message- From: Gavin Myers [mailto:[EMAIL PROTECTED]] Sent: 09 August 2000 13:41 To: '[EMAIL PROTECTED]' Subject: CFAPPLICATION - Need some advice I've decided to take a look at application.cfm too see what I can gather. I've never really used it before Now in the simplest form: application.cfm end application.cfm The only thing I am using with the application.cfm file is #session.sessionid#, and I need to carry that sessionid through pages. But, I also want to make it so that when a person leaves my site, and then goes back they don't get the same sessionid, but a brand new one. I could set an expire date, but I'd rather have it not use the same one over again automatically. Any suggestions? Oh and while were on the subject, I want to set global variables while person-x is in the site. Example: Making a shopping cart that records when a person checks on a radio button labled purchase. That way when they are 4-99 pages deep they can hit buy and bring up a list of all of the things they said yes to. So you click on yes, and it globals the name of the product and the product_id, so I can reference it later. Thanks, Gavin -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body. -- Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
