session expiration
Is there anyway to know that a user has disconnected from their session through network failure, power off, or browser closure? I am logging information about the user to a database when they login to a site, and I need to clean up this data when they leave. Obviously this is no problem with the user explicitly clicks a button to logoff, but we all know that hardly ever happens Thanks! Trey - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: session expiration
Yeah, thought about that, but that won't work if they are sitting behind a firewall. Trey Craig E Ransom wrote: Hi Trey! Is there anyway to know that a user has disconnected from their session through network failure, power off, or browser closure? How about extracting the user's IP address and then, if he hasn't sent anything over for a time period, ping him? -- Craig (The Data Ferret) http://www.pcferret.com/ for RARS, NetClip http://www.pcferret.com/teletools.html for Telephony http://www.pcferret.com/gps.html for GPS! Virtual Access 5.50 build 311 Win98 http://counter.li.org ID #184149 "Do not meddle in the affairs of FERRETS..." - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: session expiration
Well, this is the basic scenario. The same userid cannot be logged into the app more than once at any given time. Also, we want to use a cookie to keep the user from having to explicitly login everytime. The latter will be accomplished with cookies and the first rule will be enforced with a "loggedin" flag in the database. My problem lies in the user not explicitly clicking logout when they leave the site. If they explicitly click logout, i can change the "loggedin" flag to false so that they can enter again the next time they try. However, if they do not explicitly logout, I cannot fire the code to change the flag in the database. So basically I want to set a cookie that will allow them to enter the site under their userid, but I can't allow them to enter if they are currently logged in from elsewhere. Any ideas? Trey Tim Bishop wrote: On Mon, 20 Nov 2000, Bill Moseley wrote: At 03:00 PM 11/20/00 -0600, Trey Connell wrote: Is there anyway to know that a user has disconnected from their session through network failure, power off, or browser closure? How is that different from just going out for a cup of coffee or opening a new browser window and looking at a different site? I am logging information about the user to a database when they login to a site, and I need to clean up this data when they leave. Define "leave" and you will have the answer. All you can do is set an inactivity timeout, I'd suspect. cron is your friend in these cases. And spec out what you want when a user does happen to come back after you have expired their session with cron. (they leave their browser open for awhile, or they bookmark a page). -Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: session expiration
Yeah, big troubleI'm thinking the client's just retarded. ;~) Bill Moseley wrote: At 05:20 PM 11/20/00 -0600, Trey Connell wrote: The latter will be accomplished with cookies and the first rule will be enforced with a "loggedin" flag in the database. My problem lies in the user not explicitly clicking logout when they leave the site. If they explicitly click logout, i can change the "loggedin" flag to false so that they can enter again the next time they try. However, if they do not explicitly logout, I cannot fire the code to change the flag in the database. That's where cron comes in. Just make your flag a time, and update it each request. cron then removes any that are older than some preset time and *poof* they are then logged out. They try to access again and you see they have a cookie, yet are logged out and you say "Sorry, you session has expired". So basically I want to set a cookie that will allow them to enter the site under their userid, but I can't allow them to enter if they are currently logged in from elsewhere. Why? What if they want two windows open at the same time? Is that allowed? That design limitation sounds like it's going to make trouble. Bill Moseley mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Putting together the TPC mod_perl track
Could someone please tell me where and when this conference will be held? Also, how do I go about registering to attend? Many Thanks, Trey - Original Message - From: Nathan Torkington [EMAIL PROTECTED] To: Matt Sergeant [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, November 01, 2000 11:14 AM Subject: Re: Putting together the TPC mod_perl track Matt Sergeant writes: Since its getting towards the end of the year, should we be thinking of putting together a mod_perl track for TPC? I've got a room allocated to mod_perl for two days of conference at the next OScon. With this group's blessing I'd like to call it "the mod_perl conference", as nobody else is offering mod_perl this kind of exposure. It'll be mentioned in TPC advertising, but it won't be a Perl or Apache track of the conference: it'll be labelled and promoted as mod_perl only. The low-hanging fruit (obvious topics) will be: * Doug MacEachern on mod_perl 2 * Matt on AxKit (also likely to make an appearance in the XML track) * Brian on AO (please please dark gods let AO come to fruition) * talk(s) on how to do good things with Apache::ASP * mod_perl + backhand = ass-kicking * Tips for developing or tuning HTML::Mason sites * Case studies showing how big companies use mod_perl This latter is an important part of the Perl conference. Many companies who would never 'fess up to using Perl seem quite happy to send employees to speak at conferences. Their talks end up as a big advertisement for Perl, and lets us name-drop the company as a Perl user. I see no reason why the same shouldn't happen with mod_perl. Nat
