You can capture the users IP with the cgi.remote_addr variable and either place it in your db or an application scoped array or structure. Storing it in a cookie, client or session variable is no good since those variables would be user specific. If it were me, I would go with the application scoped array because I find accessing data from memory is easier than running a query.
HTH, Mark -----Original Message----- From: han peng [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 09, 2002 8:30 PM To: CF-Talk Subject: Re: how to prevent user from opening multiple browsers.. hi.. mark and lewis.. thank you very much for yr suggestions.. i'm running my application in intranet.. so mark suggestion is useful... but how do i capture the ip?? to a database..? or?? pls shed some light to it.. as for lewis.. yr method cant restrict people from having 2 different logins at same machine... and guess... if i combine these 2 suggestions together... it will solve the problem.for me..!! so still a big thank you to u both!!! : ) cheers han ----- Original Message ----- From: "Mark Stewart" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Thursday, January 10, 2002 3:11 AM Subject: RE: how to prevent user from opening multiple browsers.. > Good point and probably a little bit more cleaner. > > Mark > > > -----Original Message----- > From: Lewis Sellers [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 09, 2002 11:55 AM > To: CF-Talk > Subject: Re: how to prevent user from opening multiple browsers.. > > > On Wed, 9 Jan 2002 09:15:28 -0500, Mark Stewart <[EMAIL PROTECTED]> > wrote: > > >If I understand you correctly, once a user has logged in, you don't > want > >them to click on the IE icon or Nutscrape and go to your site and log > in > >again? If this is right, just capture their IP on login. When the next > >user logs in, make sure that the IP's aren't the same. > > In general I find that IP's are fairly worthless with anything having > to do with login's unless you are in a controlled intranet. And even > then... > > Basically the simpliest thing to do is simply use a mutex on the > user's database record. That is, a lock, or a numeric field say called > "lock" with a default of 0. When someone logs in you +1 the record. > When they log out you -1 the record. > > Don't allow any more login's when lock is >0. > > Put a timedate field for lock expiration in to allow "incidnets" to > resolves themselves after a peroid of time so the admin isn't hassled > to reset the lock. > > --min > > ______________________________________________________________________ Dedicated Windows 2000 Server PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation � $99/Month � Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusiona FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
