RE: keeping a session alive
I have an application that, after 20 mins of idle (detected by JS), the user is given a warning saying they are about to be logged out with a link to keep the session going. My original plan was to sent an AJAX request to a page when the link is clicked, but I have read that an AJAX request will not keep the session alive. Redirecting off the page is out of the question. In the past I have had the yes keep my session active option like this create an image object within JavaScript and then set the source attribute to a ColdFusion page that served up a blank image (not that it mattered since it was never displayed anywhere. This can also be used to ping the server and have data passed back in a cookie that the JS can read, a sort of poor-man's AJAX before AJAX was even a term). There are certain instances in a content management system where you may want to automatically keep the session alive longer without prompting the user, and the same method applies in the background. -Justin ~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:325494 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Re: keeping a session alive
Just off the top of my head and without doing any research into the topic. Assuming everything you said is accurate, that you can't sustain the session with an AJAX request, when your user clicks the link, it could load a 1px x1px iframe into a div on the page that loads a keep alive page, thus sustaining the session. Ideally, the ajax call will sustain the session, but testing will be requred to prove that. =] -- Alan Rother Adobe Certified Advanced ColdFusion MX 7 Developer Manager, Phoenix Cold Fusion User Group, AZCFUG.org ~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:325457 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
RE: keeping a session alive
I have read that an AJAX request will not keep the session alive. Where did you hear that? If the Ajax request is to a ColdFusion page that is part of your application it will most certainly keep the session alive. The server, after all, doesn't even know it is an Ajax call. ~Brad ~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:325458 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Re: keeping a session alive
Server: If you have a session going and it is idle up to the timeout it will end. As soon as another request happens after the timeout, a new session begins. If a request occurs before the timeout, the countdown begins all over again. Client/browser side: Seems like you need to write something that checks the time between click events and then check when the last request to the server happened by storing that in your browser every time it occurs. Otherwise, you have no way of checking without refreshing the timeout back to zero on the server. Or there is but it requires some knowledge of the server and application interactions. Either way, it is going to require both browser and server time tracking functions. ~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:325461 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
RE: keeping a session alive
Technically the server can know, via headers. http://www.developertutorials.com/learn-ajax/custom-http-headers-2643.php At least if you're using jQuery I believe that it adds this to the header automatically. -Original Message- From: b...@bradwood.com [mailto:b...@bradwood.com] Sent: Friday, August 14, 2009 3:59 PM To: cf-talk Subject: RE: keeping a session alive I have read that an AJAX request will not keep the session alive. Where did you hear that? If the Ajax request is to a ColdFusion page that is part of your application it will most certainly keep the session alive. The server, after all, doesn't even know it is an Ajax call. ~Brad ~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:325463 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
RE: keeping a session alive
Heh, I was waiting for someone to go there. Yes, you are correct that specific headers can be added to an HTTP request by the client which signal to the server that the request was made via an Ajax call. Strictly speaking though, they aren't guaranteed to exists. Regardless, the existence of such a header would in no way tell ColdFusion to ignore the usual session timeout-resetting that occurs with any other request to a ColdFusion page. ColdFusion treats Ajax requests like any other request your browser sends. ~Brad Original Message Subject: RE: keeping a session alive From: Andy Matthews li...@commadelimited.com Date: Fri, August 14, 2009 4:20 pm To: cf-talk cf-talk@houseoffusion.com Technically the server can know, via headers. http://www.developertutorials.com/learn-ajax/custom-http-headers-2643.php At least if you're using jQuery I believe that it adds this to the header automatically. -Original Message- From: b...@bradwood.com [mailto:b...@bradwood.com] Sent: Friday, August 14, 2009 3:59 PM To: cf-talk Subject: RE: keeping a session alive I have read that an AJAX request will not keep the session alive. Where did you hear that? If the Ajax request is to a ColdFusion page that is part of your application it will most certainly keep the session alive. The server, after all, doesn't even know it is an Ajax call. ~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:325464 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Re: keeping a session alive
2009/8/15 Eric Hynds e...@hynds.net: I was wondering ... if what I read was wrong and you actually can keep the session alive with an AJAX request. This is the case. mxAjax / CFAjax docs and other useful articles: http://www.bifrost.com.au/blog ~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:325467 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
RE: Keeping a session alive
Bobby, 1) I absolutely REFUSE to use a frame or Iframe whatsoever. Then you like making life hard. ;) While an frame would be the most compatible, and IFRAME should really work in every modern browser (doesn't work in Netscape 4, but if you need that you could use an ILAYER tag for NS4.) Seriously, an IFRAME would be the best way to go. 2) It wouldn't allow for seamlessly 'alerting' the user about a session that I might not be able to 'reset' and keep alive. Sure it would. Just have the IFRAME refresh itself: -- keepyoursessionalive.cfm -- cfset iRefreshInSeconds = 600 / html head meta http-equiv=refresh content=cfoutput#iRefreshInSeconds#/cfoutput / cfif structKeyExists(session, someSessionVarThatShouldExist) script type=text/javascript alert(Your session has expired.); /script /cfif /head body/body /html 3) too easy. Lol While I can probably hammer in a nail using my PSP, I'd prefer using a hammer. I know the hammer will work. The PSP will probably work, but I'm just as likely to break my PS as I am to hammer in the nail. - Dan ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225941 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
If you want to refresh, you can also use an image Make image.cfm. img name='session' src=image.cfm cfcontent type=image/gif file=some1PixelGIF Add CFHEADER for expires so it always goes back to the server Then you can make a JS in your page, which does this: // every 10 minutes setInterval(document.images['session'].src='image.cfm';,600); This will keep the session alive... -Original Message- From: Dan G. Switzer, II [mailto:[EMAIL PROTECTED] Sent: Friday, December 02, 2005 11:03 AM To: CF-Talk Subject: RE: Keeping a session alive Bobby, 1) I absolutely REFUSE to use a frame or Iframe whatsoever. Then you like making life hard. ;) While an frame would be the most compatible, and IFRAME should really work in every modern browser (doesn't work in Netscape 4, but if you need that you could use an ILAYER tag for NS4.) Seriously, an IFRAME would be the best way to go. 2) It wouldn't allow for seamlessly 'alerting' the user about a session that I might not be able to 'reset' and keep alive. Sure it would. Just have the IFRAME refresh itself: -- keepyoursessionalive.cfm -- cfset iRefreshInSeconds = 600 / html head meta http-equiv=refresh content=cfoutput#iRefreshInSeconds#/cfoutput / cfif structKeyExists(session, someSessionVarThatShouldExist) script type=text/javascript alert(Your session has expired.); /script /cfif /head body/body /html 3) too easy. Lol While I can probably hammer in a nail using my PSP, I'd prefer using a hammer. I know the hammer will work. The PSP will probably work, but I'm just as likely to break my PS as I am to hammer in the nail. - Dan ~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225942 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
Hey, thats pretty nifty there thanks. ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Katz, Dov B (IT) [mailto:[EMAIL PROTECTED] Sent: Friday, December 02, 2005 11:08 AM To: CF-Talk Subject: RE: Keeping a session alive If you want to refresh, you can also use an image Make image.cfm. img name='session' src=image.cfm cfcontent type=image/gif file=some1PixelGIF Add CFHEADER for expires so it always goes back to the server Then you can make a JS in your page, which does this: // every 10 minutes setInterval(document.images['session'].src='image.cfm';,600); This will keep the session alive... -Original Message- From: Dan G. Switzer, II [mailto:[EMAIL PROTECTED] Sent: Friday, December 02, 2005 11:03 AM To: CF-Talk Subject: RE: Keeping a session alive Bobby, 1) I absolutely REFUSE to use a frame or Iframe whatsoever. Then you like making life hard. ;) While an frame would be the most compatible, and IFRAME should really work in every modern browser (doesn't work in Netscape 4, but if you need that you could use an ILAYER tag for NS4.) Seriously, an IFRAME would be the best way to go. 2) It wouldn't allow for seamlessly 'alerting' the user about a session that I might not be able to 'reset' and keep alive. Sure it would. Just have the IFRAME refresh itself: -- keepyoursessionalive.cfm -- cfset iRefreshInSeconds = 600 / html head meta http-equiv=refresh content=cfoutput#iRefreshInSeconds#/cfoutput / cfif structKeyExists(session, someSessionVarThatShouldExist) script type=text/javascript alert(Your session has expired.); /script /cfif /head body/body /html 3) too easy. Lol While I can probably hammer in a nail using my PSP, I'd prefer using a hammer. I know the hammer will work. The PSP will probably work, but I'm just as likely to break my PS as I am to hammer in the nail. - Dan ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225943 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
Just out of curiosity... can a frame trigger a js event in another frame? Just curious since I still refuse to use one :) Thats the second time someone has mentioned 'harder' or 'more trouble'. Come on people... it's not brick work... it's programming. Nothing about it is 'hard' or 'troubling' Nice PSP analogy though ;) I've got a nice method with httprequest on a timed trigger now. It works great. ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Dan G. Switzer, II [mailto:[EMAIL PROTECTED] Sent: Friday, December 02, 2005 11:03 AM To: CF-Talk Subject: RE: Keeping a session alive Bobby, 1) I absolutely REFUSE to use a frame or Iframe whatsoever. Then you like making life hard. ;) While an frame would be the most compatible, and IFRAME should really work in every modern browser (doesn't work in Netscape 4, but if you need that you could use an ILAYER tag for NS4.) Seriously, an IFRAME would be the best way to go. 2) It wouldn't allow for seamlessly 'alerting' the user about a session that I might not be able to 'reset' and keep alive. Sure it would. Just have the IFRAME refresh itself: -- keepyoursessionalive.cfm -- cfset iRefreshInSeconds = 600 / html head meta http-equiv=refresh content=cfoutput#iRefreshInSeconds#/cfoutput / cfif structKeyExists(session, someSessionVarThatShouldExist) script type=text/javascript alert(Your session has expired.); /script /cfif /head body/body /html 3) too easy. Lol While I can probably hammer in a nail using my PSP, I'd prefer using a hammer. I know the hammer will work. The PSP will probably work, but I'm just as likely to break my PS as I am to hammer in the nail. - Dan ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225944 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
Re: Keeping a session alive
1) I absolutely REFUSE to use a frame or Iframe whatsoever. You're right. Have a look at XMLHttpRequest in Javascript. You can call a CF template every 10 min or so, directly from a script, without having to reload any part of the page, no blink, no glass cursor, no nothing. The user will see nothing. -- ___ REUSE CODE! Use custom tags; See http://www.contentbox.com/claude/customtags/tagstore.cfm (Please send any spam to this address: [EMAIL PROTECTED]) Thanks. ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225946 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
This is probably what I meant when I said use AJAX. -Original Message- From: Claude Schneegans [mailto:[EMAIL PROTECTED] Sent: Friday, December 02, 2005 11:25 AM To: CF-Talk Subject: Re: Keeping a session alive 1) I absolutely REFUSE to use a frame or Iframe whatsoever. You're right. Have a look at XMLHttpRequest in Javascript. You can call a CF template every 10 min or so, directly from a script, without having to reload any part of the page, no blink, no glass cursor, no nothing. The user will see nothing. -- ___ REUSE CODE! Use custom tags; See http://www.contentbox.com/claude/customtags/tagstore.cfm (Please send any spam to this address: [EMAIL PROTECTED]) Thanks. ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225952 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
-Original Message- From: Katz, Dov B (IT) [mailto:[EMAIL PROTECTED] Sent: Friday, December 02, 2005 11:08 AM To: CF-Talk Subject: RE: Keeping a session alive If you want to refresh, you can also use an image I've an extensive article and sample code for using a GIF as a data pipe here: http://www.depressedpress.com/Content/Development/JavaScript/Articles/GIFAsP ipe/Index.cfm The article also provides the JavaScript code needed to parse responses from the server using this. Hope it helps, Jim Davis ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225954 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
Nice. Just one of the MANY useful reads at depressedpress.com :) Thanks Jim. ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Jim Davis [mailto:[EMAIL PROTECTED] Sent: Friday, December 02, 2005 12:00 PM To: CF-Talk Subject: RE: Keeping a session alive -Original Message- From: Katz, Dov B (IT) [mailto:[EMAIL PROTECTED] Sent: Friday, December 02, 2005 11:08 AM To: CF-Talk Subject: RE: Keeping a session alive If you want to refresh, you can also use an image I've an extensive article and sample code for using a GIF as a data pipe here: http://www.depressedpress.com/Content/Development/JavaScript/Articles/GIFAsP ipe/Index.cfm The article also provides the JavaScript code needed to parse responses from the server using this. Hope it helps, Jim Davis ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225958 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
Re: Keeping a session alive
This is probably what I meant when I said use AJAX. Probabily, although AJAX may be a big word when only a couple of lines of code are needed in this case. ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225962 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
Bobby, Just out of curiosity... can a frame trigger a js event in another frame? Provider there are the same domain (which is usually the case,) yes. Just use the parent object to reference the document object that created the iframe /. Just curious since I still refuse to use one :) That's the second time someone has mentioned 'harder' or 'more trouble'. Come on people... it's not brick work... it's programming. Nothing about it is 'hard' or 'troubling' Nice PSP analogy though ;) I've got a nice method with httprequest on a timed trigger now. It works great. Just remember that the xmlHttpRequest object could open up compatibility problems between different browsers. It just seems like overkill for you need. -Dan ~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225968 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
Re: Keeping a session alive
Ive got a js routine that does just this. Basically you set it to a minute less than your session timeout. If it expires, it reloads the page they are on. Just dont want to use it with any pages that you post to. Let me know if you want it. On 12/1/05, Bobby Hartsfield [EMAIL PROTECTED] wrote: Hello there... I've been kicking around ideas of how to keep a user's session 'alive' once they get logged in on a site. The scenario is a common one... An admin logs into the backend tools to add something. They sit on a form typing in a long, long news article or something When they are finally done an hour later, they go to submit it and their session has died and they have to log in again... then all the info they entered is gone and I get yelled at. :) I do NOT want to use cookies on these sections so I need something to keep hitting a page (really any page I guess) in the background to keep the session alive as long as their browser is open. I thought about a frame with a meta refreshed page in it but that's not very creative :) I thought about a tiny swf to do basically the same thing... that's a little better I guess. And I thought about a JS routine to occasionally fire itself based on a timer to do an httprequest to another page that will: Check the session (if it's still active, that would reset its timeout right?) If it's active, return active or whatever. If it's inactive, pass along the encrypted login info to log them back in and return active If for any reason the session is dead and cant be reset, return inactive so a hidden div or JS alert can inform them to at least copy what they have written in the field so they don't lose it because they are going to have to log in again. If the user ever got to the page, their session was active and valid so any login info could be ported from the session scope the variables scope on that page and used anytime I wanted. (like for logging them back in) I obviously like the last 'idea' better due to the elaboration :) but wanted to know what others thought about it or if you guys and gals had another solution I haven't thought of. (short of turning the session timeout up to some ridiculous amount of time) ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.10/189 - Release Date: 11/30/2005 ~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225848 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
so if they are in the middle of typing War and Peace in a form field when the JS kicks off, they lose it all? Mike -Original Message- From: Ryan Guill [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 1:22 PM To: CF-Talk Subject: Re: Keeping a session alive Ive got a js routine that does just this. Basically you set it to a minute less than your session timeout. If it expires, it reloads the page they are on. Just dont want to use it with any pages that you post to. Let me know if you want it. On 12/1/05, Bobby Hartsfield [EMAIL PROTECTED] wrote: Hello there... I've been kicking around ideas of how to keep a user's session 'alive' once they get logged in on a site. The scenario is a common one... An admin logs into the backend tools to add something. They sit on a form typing in a long, long news article or something When they are finally done an hour later, they go to submit it and their session has died and they have to log in again... then all the info they entered is gone and I get yelled at. :) I do NOT want to use cookies on these sections so I need something to keep hitting a page (really any page I guess) in the background to keep the session alive as long as their browser is open. I thought about a frame with a meta refreshed page in it but that's not very creative :) I thought about a tiny swf to do basically the same thing... that's a little better I guess. And I thought about a JS routine to occasionally fire itself based on a timer to do an httprequest to another page that will: Check the session (if it's still active, that would reset its timeout right?) If it's active, return active or whatever. If it's inactive, pass along the encrypted login info to log them back in and return active If for any reason the session is dead and cant be reset, return inactive so a hidden div or JS alert can inform them to at least copy what they have written in the field so they don't lose it because they are going to have to log in again. If the user ever got to the page, their session was active and valid so any login info could be ported from the session scope the variables scope on that page and used anytime I wanted. (like for logging them back in) I obviously like the last 'idea' better due to the elaboration :) but wanted to know what others thought about it or if you guys and gals had another solution I haven't thought of. (short of turning the session timeout up to some ridiculous amount of time) ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.10/189 - Release Date: 11/30/2005 ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225849 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
Re: Keeping a session alive
Yeah, but with a 2 hours sessiontimeout, they would have to be doing exactly that, writing a novel. Also, after less than an hour is left (meaning they have already taken an hour), it counts down in the status bar, telling them how long they have in minutes. After a minute or less is left, it counts down in seconds. On 12/1/05, Mike Klostermeyer [EMAIL PROTECTED] wrote: so if they are in the middle of typing War and Peace in a form field when the JS kicks off, they lose it all? Mike -Original Message- From: Ryan Guill [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 1:22 PM To: CF-Talk Subject: Re: Keeping a session alive Ive got a js routine that does just this. Basically you set it to a minute less than your session timeout. If it expires, it reloads the page they are on. Just dont want to use it with any pages that you post to. Let me know if you want it. On 12/1/05, Bobby Hartsfield [EMAIL PROTECTED] wrote: Hello there... I've been kicking around ideas of how to keep a user's session 'alive' once they get logged in on a site. The scenario is a common one... An admin logs into the backend tools to add something. They sit on a form typing in a long, long news article or something When they are finally done an hour later, they go to submit it and their session has died and they have to log in again... then all the info they entered is gone and I get yelled at. :) I do NOT want to use cookies on these sections so I need something to keep hitting a page (really any page I guess) in the background to keep the session alive as long as their browser is open. I thought about a frame with a meta refreshed page in it but that's not very creative :) I thought about a tiny swf to do basically the same thing... that's a little better I guess. And I thought about a JS routine to occasionally fire itself based on a timer to do an httprequest to another page that will: Check the session (if it's still active, that would reset its timeout right?) If it's active, return active or whatever. If it's inactive, pass along the encrypted login info to log them back in and return active If for any reason the session is dead and cant be reset, return inactive so a hidden div or JS alert can inform them to at least copy what they have written in the field so they don't lose it because they are going to have to log in again. If the user ever got to the page, their session was active and valid so any login info could be ported from the session scope the variables scope on that page and used anytime I wanted. (like for logging them back in) I obviously like the last 'idea' better due to the elaboration :) but wanted to know what others thought about it or if you guys and gals had another solution I haven't thought of. (short of turning the session timeout up to some ridiculous amount of time) ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.10/189 - Release Date: 11/30/2005 ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225850 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
Only if the session dies before they submit it. In that case, they are sent to the login form and the forms post is lost. ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Mike Klostermeyer [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 2:25 PM To: CF-Talk Subject: RE: Keeping a session alive so if they are in the middle of typing War and Peace in a form field when the JS kicks off, they lose it all? Mike -Original Message- From: Ryan Guill [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 1:22 PM To: CF-Talk Subject: Re: Keeping a session alive Ive got a js routine that does just this. Basically you set it to a minute less than your session timeout. If it expires, it reloads the page they are on. Just dont want to use it with any pages that you post to. Let me know if you want it. On 12/1/05, Bobby Hartsfield [EMAIL PROTECTED] wrote: Hello there... I've been kicking around ideas of how to keep a user's session 'alive' once they get logged in on a site. The scenario is a common one... An admin logs into the backend tools to add something. They sit on a form typing in a long, long news article or something When they are finally done an hour later, they go to submit it and their session has died and they have to log in again... then all the info they entered is gone and I get yelled at. :) I do NOT want to use cookies on these sections so I need something to keep hitting a page (really any page I guess) in the background to keep the session alive as long as their browser is open. I thought about a frame with a meta refreshed page in it but that's not very creative :) I thought about a tiny swf to do basically the same thing... that's a little better I guess. And I thought about a JS routine to occasionally fire itself based on a timer to do an httprequest to another page that will: Check the session (if it's still active, that would reset its timeout right?) If it's active, return active or whatever. If it's inactive, pass along the encrypted login info to log them back in and return active If for any reason the session is dead and cant be reset, return inactive so a hidden div or JS alert can inform them to at least copy what they have written in the field so they don't lose it because they are going to have to log in again. If the user ever got to the page, their session was active and valid so any login info could be ported from the session scope the variables scope on that page and used anytime I wanted. (like for logging them back in) I obviously like the last 'idea' better due to the elaboration :) but wanted to know what others thought about it or if you guys and gals had another solution I haven't thought of. (short of turning the session timeout up to some ridiculous amount of time) ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.10/189 - Release Date: 11/30/2005 ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225852 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
Very much appreciated. I really was just curious of what others thought about the idea... pros/cons... that sort of thing. I'd enjoy writing something like this too much to have it handed to me :) ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Ryan Guill [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 2:22 PM To: CF-Talk Subject: Re: Keeping a session alive Ive got a js routine that does just this. Basically you set it to a minute less than your session timeout. If it expires, it reloads the page they are on. Just dont want to use it with any pages that you post to. Let me know if you want it. On 12/1/05, Bobby Hartsfield [EMAIL PROTECTED] wrote: Hello there... I've been kicking around ideas of how to keep a user's session 'alive' once they get logged in on a site. The scenario is a common one... An admin logs into the backend tools to add something. They sit on a form typing in a long, long news article or something When they are finally done an hour later, they go to submit it and their session has died and they have to log in again... then all the info they entered is gone and I get yelled at. :) I do NOT want to use cookies on these sections so I need something to keep hitting a page (really any page I guess) in the background to keep the session alive as long as their browser is open. I thought about a frame with a meta refreshed page in it but that's not very creative :) I thought about a tiny swf to do basically the same thing... that's a little better I guess. And I thought about a JS routine to occasionally fire itself based on a timer to do an httprequest to another page that will: Check the session (if it's still active, that would reset its timeout right?) If it's active, return active or whatever. If it's inactive, pass along the encrypted login info to log them back in and return active If for any reason the session is dead and cant be reset, return inactive so a hidden div or JS alert can inform them to at least copy what they have written in the field so they don't lose it because they are going to have to log in again. If the user ever got to the page, their session was active and valid so any login info could be ported from the session scope the variables scope on that page and used anytime I wanted. (like for logging them back in) I obviously like the last 'idea' better due to the elaboration :) but wanted to know what others thought about it or if you guys and gals had another solution I haven't thought of. (short of turning the session timeout up to some ridiculous amount of time) ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.10/189 - Release Date: 11/30/2005 ~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225854 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
Re: Keeping a session alive
LOL, thats fine too. If you decide you want something to work from though, just let me know. On 12/1/05, Bobby Hartsfield [EMAIL PROTECTED] wrote: Very much appreciated. I really was just curious of what others thought about the idea... pros/cons... that sort of thing. I'd enjoy writing something like this too much to have it handed to me :) ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Ryan Guill [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 2:22 PM To: CF-Talk Subject: Re: Keeping a session alive Ive got a js routine that does just this. Basically you set it to a minute less than your session timeout. If it expires, it reloads the page they are on. Just dont want to use it with any pages that you post to. Let me know if you want it. On 12/1/05, Bobby Hartsfield [EMAIL PROTECTED] wrote: Hello there... I've been kicking around ideas of how to keep a user's session 'alive' once they get logged in on a site. The scenario is a common one... An admin logs into the backend tools to add something. They sit on a form typing in a long, long news article or something When they are finally done an hour later, they go to submit it and their session has died and they have to log in again... then all the info they entered is gone and I get yelled at. :) I do NOT want to use cookies on these sections so I need something to keep hitting a page (really any page I guess) in the background to keep the session alive as long as their browser is open. I thought about a frame with a meta refreshed page in it but that's not very creative :) I thought about a tiny swf to do basically the same thing... that's a little better I guess. And I thought about a JS routine to occasionally fire itself based on a timer to do an httprequest to another page that will: Check the session (if it's still active, that would reset its timeout right?) If it's active, return active or whatever. If it's inactive, pass along the encrypted login info to log them back in and return active If for any reason the session is dead and cant be reset, return inactive so a hidden div or JS alert can inform them to at least copy what they have written in the field so they don't lose it because they are going to have to log in again. If the user ever got to the page, their session was active and valid so any login info could be ported from the session scope the variables scope on that page and used anytime I wanted. (like for logging them back in) I obviously like the last 'idea' better due to the elaboration :) but wanted to know what others thought about it or if you guys and gals had another solution I haven't thought of. (short of turning the session timeout up to some ridiculous amount of time) ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.10/189 - Release Date: 11/30/2005 ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225857 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
Why not use a frame or an iframe to load a page on the server in the background? This way they won't have to lose the current session (or their war and peace novel). And maybe it's possible to use ajax for this? -Original Message- From: Bobby Hartsfield [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 2:58 PM To: CF-Talk Subject: RE: Keeping a session alive Very much appreciated. I really was just curious of what others thought about the idea... pros/cons... that sort of thing. I'd enjoy writing something like this too much to have it handed to me :) ...:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Ryan Guill [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 2:22 PM To: CF-Talk Subject: Re: Keeping a session alive Ive got a js routine that does just this. Basically you set it to a minute less than your session timeout. If it expires, it reloads the page they are on. Just dont want to use it with any pages that you post to. Let me know if you want it. On 12/1/05, Bobby Hartsfield [EMAIL PROTECTED] wrote: Hello there... I've been kicking around ideas of how to keep a user's session 'alive' once they get logged in on a site. The scenario is a common one... An admin logs into the backend tools to add something. They sit on a form typing in a long, long news article or something When they are finally done an hour later, they go to submit it and their session has died and they have to log in again... then all the info they entered is gone and I get yelled at. :) I do NOT want to use cookies on these sections so I need something to keep hitting a page (really any page I guess) in the background to keep the session alive as long as their browser is open. I thought about a frame with a meta refreshed page in it but that's not very creative :) I thought about a tiny swf to do basically the same thing... that's a little better I guess. And I thought about a JS routine to occasionally fire itself based on a timer to do an httprequest to another page that will: Check the session (if it's still active, that would reset its timeout right?) If it's active, return active or whatever. If it's inactive, pass along the encrypted login info to log them back in and return active If for any reason the session is dead and cant be reset, return inactive so a hidden div or JS alert can inform them to at least copy what they have written in the field so they don't lose it because they are going to have to log in again. If the user ever got to the page, their session was active and valid so any login info could be ported from the session scope the variables scope on that page and used anytime I wanted. (like for logging them back in) I obviously like the last 'idea' better due to the elaboration :) but wanted to know what others thought about it or if you guys and gals had another solution I haven't thought of. (short of turning the session timeout up to some ridiculous amount of time) ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.10/189 - Release Date: 11/30/2005 ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225858 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
Like I said in the original post, both are options I've thought of but if you've got any pros or cons on either I'd love to hear them (other than the obvious of course... I'm not against forcing users to enable JS on the backend at all) ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Russ [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 3:10 PM To: CF-Talk Subject: RE: Keeping a session alive Why not use a frame or an iframe to load a page on the server in the background? This way they won't have to lose the current session (or their war and peace novel). And maybe it's possible to use ajax for this? -Original Message- From: Bobby Hartsfield [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 2:58 PM To: CF-Talk Subject: RE: Keeping a session alive Very much appreciated. I really was just curious of what others thought about the idea... pros/cons... that sort of thing. I'd enjoy writing something like this too much to have it handed to me :) :.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Ryan Guill [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 2:22 PM To: CF-Talk Subject: Re: Keeping a session alive Ive got a js routine that does just this. Basically you set it to a minute less than your session timeout. If it expires, it reloads the page they are on. Just dont want to use it with any pages that you post to. Let me know if you want it. On 12/1/05, Bobby Hartsfield [EMAIL PROTECTED] wrote: Hello there... I've been kicking around ideas of how to keep a user's session 'alive' once they get logged in on a site. The scenario is a common one... An admin logs into the backend tools to add something. They sit on a form typing in a long, long news article or something When they are finally done an hour later, they go to submit it and their session has died and they have to log in again... then all the info they entered is gone and I get yelled at. :) I do NOT want to use cookies on these sections so I need something to keep hitting a page (really any page I guess) in the background to keep the session alive as long as their browser is open. I thought about a frame with a meta refreshed page in it but that's not very creative :) I thought about a tiny swf to do basically the same thing... that's a little better I guess. And I thought about a JS routine to occasionally fire itself based on a timer to do an httprequest to another page that will: Check the session (if it's still active, that would reset its timeout right?) If it's active, return active or whatever. If it's inactive, pass along the encrypted login info to log them back in and return active If for any reason the session is dead and cant be reset, return inactive so a hidden div or JS alert can inform them to at least copy what they have written in the field so they don't lose it because they are going to have to log in again. If the user ever got to the page, their session was active and valid so any login info could be ported from the session scope the variables scope on that page and used anytime I wanted. (like for logging them back in) I obviously like the last 'idea' better due to the elaboration :) but wanted to know what others thought about it or if you guys and gals had another solution I haven't thought of. (short of turning the session timeout up to some ridiculous amount of time) ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.10/189 - Release Date: 11/30/2005 ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225860 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
Well if you use an iframe, you can set it to a page that reloads every few seconds (minutes). No javascript needed, just META REFRESH. Same with Frame. But Frame would require you to build your site using frames (yuck). I would really love an AJAX implementation. I believe AJAX posts cookies to the site, and that is all that's required to keep the session active. -Original Message- From: Bobby Hartsfield [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 3:16 PM To: CF-Talk Subject: RE: Keeping a session alive Like I said in the original post, both are options I've thought of but if you've got any pros or cons on either I'd love to hear them (other than the obvious of course... I'm not against forcing users to enable JS on the backend at all) ...:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Russ [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 3:10 PM To: CF-Talk Subject: RE: Keeping a session alive Why not use a frame or an iframe to load a page on the server in the background? This way they won't have to lose the current session (or their war and peace novel). And maybe it's possible to use ajax for this? -Original Message- From: Bobby Hartsfield [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 2:58 PM To: CF-Talk Subject: RE: Keeping a session alive Very much appreciated. I really was just curious of what others thought about the idea... pros/cons... that sort of thing. I'd enjoy writing something like this too much to have it handed to me :) .:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Ryan Guill [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 2:22 PM To: CF-Talk Subject: Re: Keeping a session alive Ive got a js routine that does just this. Basically you set it to a minute less than your session timeout. If it expires, it reloads the page they are on. Just dont want to use it with any pages that you post to. Let me know if you want it. On 12/1/05, Bobby Hartsfield [EMAIL PROTECTED] wrote: Hello there... I've been kicking around ideas of how to keep a user's session 'alive' once they get logged in on a site. The scenario is a common one... An admin logs into the backend tools to add something. They sit on a form typing in a long, long news article or something When they are finally done an hour later, they go to submit it and their session has died and they have to log in again... then all the info they entered is gone and I get yelled at. :) I do NOT want to use cookies on these sections so I need something to keep hitting a page (really any page I guess) in the background to keep the session alive as long as their browser is open. I thought about a frame with a meta refreshed page in it but that's not very creative :) I thought about a tiny swf to do basically the same thing... that's a little better I guess. And I thought about a JS routine to occasionally fire itself based on a timer to do an httprequest to another page that will: Check the session (if it's still active, that would reset its timeout right?) If it's active, return active or whatever. If it's inactive, pass along the encrypted login info to log them back in and return active If for any reason the session is dead and cant be reset, return inactive so a hidden div or JS alert can inform them to at least copy what they have written in the field so they don't lose it because they are going to have to log in again. If the user ever got to the page, their session was active and valid so any login info could be ported from the session scope the variables scope on that page and used anytime I wanted. (like for logging them back in) I obviously like the last 'idea' better due to the elaboration :) but wanted to know what others thought about it or if you guys and gals had another solution I haven't thought of. (short of turning the session timeout up to some ridiculous amount of time) ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.10/189 - Release Date: 11/30/2005 ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225862 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm
RE: Keeping a session alive
Yeah, yuck on the frames. The httprequest leaves much more room for creativity as well. Thanks for the input ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Russ [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 3:27 PM To: CF-Talk Subject: RE: Keeping a session alive Well if you use an iframe, you can set it to a page that reloads every few seconds (minutes). No javascript needed, just META REFRESH. Same with Frame. But Frame would require you to build your site using frames (yuck). I would really love an AJAX implementation. I believe AJAX posts cookies to the site, and that is all that's required to keep the session active. -Original Message- From: Bobby Hartsfield [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 3:16 PM To: CF-Talk Subject: RE: Keeping a session alive Like I said in the original post, both are options I've thought of but if you've got any pros or cons on either I'd love to hear them (other than the obvious of course... I'm not against forcing users to enable JS on the backend at all) :.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Russ [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 3:10 PM To: CF-Talk Subject: RE: Keeping a session alive Why not use a frame or an iframe to load a page on the server in the background? This way they won't have to lose the current session (or their war and peace novel). And maybe it's possible to use ajax for this? -Original Message- From: Bobby Hartsfield [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 2:58 PM To: CF-Talk Subject: RE: Keeping a session alive Very much appreciated. I really was just curious of what others thought about the idea... pros/cons... that sort of thing. I'd enjoy writing something like this too much to have it handed to me :) ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Ryan Guill [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 2:22 PM To: CF-Talk Subject: Re: Keeping a session alive Ive got a js routine that does just this. Basically you set it to a minute less than your session timeout. If it expires, it reloads the page they are on. Just dont want to use it with any pages that you post to. Let me know if you want it. On 12/1/05, Bobby Hartsfield [EMAIL PROTECTED] wrote: Hello there... I've been kicking around ideas of how to keep a user's session 'alive' once they get logged in on a site. The scenario is a common one... An admin logs into the backend tools to add something. They sit on a form typing in a long, long news article or something When they are finally done an hour later, they go to submit it and their session has died and they have to log in again... then all the info they entered is gone and I get yelled at. :) I do NOT want to use cookies on these sections so I need something to keep hitting a page (really any page I guess) in the background to keep the session alive as long as their browser is open. I thought about a frame with a meta refreshed page in it but that's not very creative :) I thought about a tiny swf to do basically the same thing... that's a little better I guess. And I thought about a JS routine to occasionally fire itself based on a timer to do an httprequest to another page that will: Check the session (if it's still active, that would reset its timeout right?) If it's active, return active or whatever. If it's inactive, pass along the encrypted login info to log them back in and return active If for any reason the session is dead and cant be reset, return inactive so a hidden div or JS alert can inform them to at least copy what they have written in the field so they don't lose it because they are going to have to log in again. If the user ever got to the page, their session was active and valid so any login info could be ported from the session scope the variables scope on that page and used anytime I wanted. (like for logging them back in) I obviously like the last 'idea' better due to the elaboration :) but wanted to know what others thought about it or if you guys and gals had another solution I haven't thought of. (short of turning the session timeout up to some ridiculous amount of time) ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.10/189 - Release Date: 11/30/2005 ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners
RE: Keeping a session alive
If you code your pages correctly, you can still have the form submitted to its final destination. Let me try to describe this: 1. User logs in and session is created. 2. User types long form, needs a smoke break and takes off for a two-hour lunch. 3. The session times out. 4. The user returns and finishes typing the form and submits it. 5. The application.cfc/.cfm catches the form submission, and checks to see if the session exists. 6. The session does not exist, so the form data is packaged in WDDX or is stored in hidden form fields. 7. The user gets a login screen to re-authenticate. The form data is passed along as well. 8. Once authenticated, the form is then posted to the originally-requested action page. Don't ask for code because I have not done this before, but it sounds like it should work, huh? M!ke -Original Message- From: Bobby Hartsfield [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 1:56 PM To: CF-Talk Subject: RE: Keeping a session alive Only if the session dies before they submit it. In that case, they are sent to the login form and the forms post is lost. ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225867 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
Re: Keeping a session alive
How would you force a post on re-authentication? On 12/1/05, Dawson, Michael [EMAIL PROTECTED] wrote: If you code your pages correctly, you can still have the form submitted to its final destination. Let me try to describe this: 1. User logs in and session is created. 2. User types long form, needs a smoke break and takes off for a two-hour lunch. 3. The session times out. 4. The user returns and finishes typing the form and submits it. 5. The application.cfc/.cfm catches the form submission, and checks to see if the session exists. 6. The session does not exist, so the form data is packaged in WDDX or is stored in hidden form fields. 7. The user gets a login screen to re-authenticate. The form data is passed along as well. 8. Once authenticated, the form is then posted to the originally-requested action page. Don't ask for code because I have not done this before, but it sounds like it should work, huh? M!ke -Original Message- From: Bobby Hartsfield [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 1:56 PM To: CF-Talk Subject: RE: Keeping a session alive Only if the session dies before they submit it. In that case, they are sent to the login form and the forms post is lost. ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225870 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
Yeah, it sounds like it would work (for the most part) but it would probably have to be stored in a session of its own and used to populate the form again since the form scope would have to keep 'posting' to the next page in the login process to keep it alive until the end. I can't think of a way to post it to the action page 'automagically after logging the user back in though... *takes a short break to let brain churn* I guess if the data was passed to the action page (by any means necessary), it could always be put back into the form scope there and wouldnt really NEED to be 'posted'. Hmmm Definitely some good ideas along those methods too. Thanks. ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Dawson, Michael [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 3:57 PM To: CF-Talk Subject: RE: Keeping a session alive If you code your pages correctly, you can still have the form submitted to its final destination. Let me try to describe this: 1. User logs in and session is created. 2. User types long form, needs a smoke break and takes off for a two-hour lunch. 3. The session times out. 4. The user returns and finishes typing the form and submits it. 5. The application.cfc/.cfm catches the form submission, and checks to see if the session exists. 6. The session does not exist, so the form data is packaged in WDDX or is stored in hidden form fields. 7. The user gets a login screen to re-authenticate. The form data is passed along as well. 8. Once authenticated, the form is then posted to the originally-requested action page. Don't ask for code because I have not done this before, but it sounds like it should work, huh? M!ke -Original Message- From: Bobby Hartsfield [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 1:56 PM To: CF-Talk Subject: RE: Keeping a session alive Only if the session dies before they submit it. In that case, they are sent to the login form and the forms post is lost. ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225872 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
Why are you thinking so complicated? A simple 1x1 pixel iframe that goes to a refresh.cfm page should do the trick. And the page can be refreshed using javascript or meta refresh without affecting the main page that the user is working on. -Original Message- From: Bobby Hartsfield [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 4:33 PM To: CF-Talk Subject: RE: Keeping a session alive Yeah, it sounds like it would work (for the most part) but it would probably have to be stored in a session of its own and used to populate the form again since the form scope would have to keep 'posting' to the next page in the login process to keep it alive until the end. I can't think of a way to post it to the action page 'automagically after logging the user back in though... *takes a short break to let brain churn* I guess if the data was passed to the action page (by any means necessary), it could always be put back into the form scope there and wouldn't really NEED to be 'posted'. Hmmm Definitely some good ideas along those methods too. Thanks. ...:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Dawson, Michael [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 3:57 PM To: CF-Talk Subject: RE: Keeping a session alive If you code your pages correctly, you can still have the form submitted to its final destination. Let me try to describe this: 1. User logs in and session is created. 2. User types long form, needs a smoke break and takes off for a two-hour lunch. 3. The session times out. 4. The user returns and finishes typing the form and submits it. 5. The application.cfc/.cfm catches the form submission, and checks to see if the session exists. 6. The session does not exist, so the form data is packaged in WDDX or is stored in hidden form fields. 7. The user gets a login screen to re-authenticate. The form data is passed along as well. 8. Once authenticated, the form is then posted to the originally-requested action page. Don't ask for code because I have not done this before, but it sounds like it should work, huh? M!ke -Original Message- From: Bobby Hartsfield [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 1:56 PM To: CF-Talk Subject: RE: Keeping a session alive Only if the session dies before they submit it. In that case, they are sent to the login form and the forms post is lost. ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225874 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
Maybe I missed something earlier in the thread, but why not just make the session time out longer, like a Day, or 4 hours. Why go though all this trouble when a long session timeout would accomplish the same thing?? ... Ben Nadel Web Developer Nylon Technology 6 West 14th Street New York, NY 10011 212.691.1134 212.691.3477 fax www.nylontechnology.com Vote for Pedro ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225876 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
1) I absolutely REFUSE to use a frame or Iframe whatsoever. 2) It wouldnt allow for seamlessly 'alerting' the user about a session that I might not be able to 'reset' and keep alive. 3) too easy. lol ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Russ [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 4:49 PM To: CF-Talk Subject: RE: Keeping a session alive Why are you thinking so complicated? A simple 1x1 pixel iframe that goes to a refresh.cfm page should do the trick. And the page can be refreshed using javascript or meta refresh without affecting the main page that the user is working on. -Original Message- From: Bobby Hartsfield [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 4:33 PM To: CF-Talk Subject: RE: Keeping a session alive Yeah, it sounds like it would work (for the most part) but it would probably have to be stored in a session of its own and used to populate the form again since the form scope would have to keep 'posting' to the next page in the login process to keep it alive until the end. I can't think of a way to post it to the action page 'automagically after logging the user back in though... *takes a short break to let brain churn* I guess if the data was passed to the action page (by any means necessary), it could always be put back into the form scope there and wouldn't really NEED to be 'posted'. Hmmm Definitely some good ideas along those methods too. Thanks. :.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Dawson, Michael [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 3:57 PM To: CF-Talk Subject: RE: Keeping a session alive If you code your pages correctly, you can still have the form submitted to its final destination. Let me try to describe this: 1. User logs in and session is created. 2. User types long form, needs a smoke break and takes off for a two-hour lunch. 3. The session times out. 4. The user returns and finishes typing the form and submits it. 5. The application.cfc/.cfm catches the form submission, and checks to see if the session exists. 6. The session does not exist, so the form data is packaged in WDDX or is stored in hidden form fields. 7. The user gets a login screen to re-authenticate. The form data is passed along as well. 8. Once authenticated, the form is then posted to the originally-requested action page. Don't ask for code because I have not done this before, but it sounds like it should work, huh? M!ke -Original Message- From: Bobby Hartsfield [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 1:56 PM To: CF-Talk Subject: RE: Keeping a session alive Only if the session dies before they submit it. In that case, they are sent to the login form and the forms post is lost. ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225878 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
Maybe I missed something earlier in the thread Yeah, last sentence of the original post. I'd never set a session for 4 days but it wouldnt accomplish the same thing anyway. 4 days of no activity would timeout :) besides...it's not 'trouble' it's fun. ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Ben Nadel [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 4:56 PM To: CF-Talk Subject: RE: Keeping a session alive Maybe I missed something earlier in the thread, but why not just make the session time out longer, like a Day, or 4 hours. Why go though all this trouble when a long session timeout would accomplish the same thing?? Ben Nadel Web Developer Nylon Technology 6 West 14th Street New York, NY 10011 212.691.1134 212.691.3477 fax www.nylontechnology.com Vote for Pedro ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225879 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
Re: Keeping a session alive
Keeping the session timeout also increases the memory usage on the cf server. Or at least creates the potential to. It locks up that memory being used for longer. On 12/1/05, Bobby Hartsfield [EMAIL PROTECTED] wrote: Maybe I missed something earlier in the thread Yeah, last sentence of the original post. I'd never set a session for 4 days but it wouldn't accomplish the same thing anyway. 4 days of no activity would timeout :) besides...it's not 'trouble' it's fun. ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Ben Nadel [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 4:56 PM To: CF-Talk Subject: RE: Keeping a session alive Maybe I missed something earlier in the thread, but why not just make the session time out longer, like a Day, or 4 hours. Why go though all this trouble when a long session timeout would accomplish the same thing?? Ben Nadel Web Developer Nylon Technology 6 West 14th Street New York, NY 10011 212.691.1134 212.691.3477 fax www.nylontechnology.com Vote for Pedro ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225882 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
Pass a WDDX packet, use hidden form fields and then a javascript form submit. There are probably a few other ways. -Original Message- From: Ryan Guill [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 3:22 PM To: CF-Talk Subject: Re: Keeping a session alive How would you force a post on re-authentication? On 12/1/05, Dawson, Michael [EMAIL PROTECTED] wrote: If you code your pages correctly, you can still have the form submitted to its final destination. Let me try to describe this: 1. User logs in and session is created. 2. User types long form, needs a smoke break and takes off for a two-hour lunch. 3. The session times out. 4. The user returns and finishes typing the form and submits it. 5. The application.cfc/.cfm catches the form submission, and checks to see if the session exists. 6. The session does not exist, so the form data is packaged in WDDX or is stored in hidden form fields. 7. The user gets a login screen to re-authenticate. The form data is passed along as well. 8. Once authenticated, the form is then posted to the originally-requested action page. Don't ask for code because I have not done this before, but it sounds like it should work, huh? M!ke ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225886 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
Why not set the session timeout to be a very large value? It seems almost pointless to have the keep-alive ping yet still want to keep the site authenticated? M!ke -Original Message- From: Russ [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 3:49 PM To: CF-Talk Subject: RE: Keeping a session alive Why are you thinking so complicated? A simple 1x1 pixel iframe that goes to a refresh.cfm page should do the trick. And the page can be refreshed using javascript or meta refresh without affecting the main page that the user is working on. ~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225888 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
Why not set the session timeout to be a very large value? It seems almost pointless to have the keep-alive ping yet still want to keep the site authenticated? One reason you might do this is to keep a session alive as long as the browser is actually open and pointing to that site, but kill the session quickly as soon as that isn't the case. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225893 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Keeping a session alive
Not just one reason but THE reason :) ..:.:.:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Dave Watts [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 6:40 PM To: CF-Talk Subject: RE: Keeping a session alive Why not set the session timeout to be a very large value? It seems almost pointless to have the keep-alive ping yet still want to keep the site authenticated? One reason you might do this is to keep a session alive as long as the browser is actually open and pointing to that site, but kill the session quickly as soon as that isn't the case. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:225896 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
