my suggestion would be an APPLICATION scope variable of those logged in at
the present time, along with their time of last activity. this is updated
for each user on every page call to the secure area. when someone tries to
log in, check the "currently logged in" structure (or data element of
choice. i would use a struct with userid or username or something as the
key) for folks already logged in under that username.
chris olive, cio
cresco technologies
[EMAIL PROTECTED]
http://www.crescotech.com
-----Original Message-----
From: Peter Alexandrou [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 17, 2000 7:37 PM
To: CF-Talk
Subject: Preventing Simultaneous Logins
Hi guys,
I'm new to the mailing list and have a quick question for y'all.
What is the best way to prevent a userID being logged in twice i.e. someone
logs in with "login1" and then another user logs in with the same ID.
Thanks,
Peter Alexandrou
Technical Leader
tapestry communications : www.tapestry.net.au
phone : 0411 445 111
e-mail : [EMAIL PROTECTED]
----------------------------------------------------------------------------
--------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a
message with 'unsubscribe' in the body to [EMAIL PROTECTED]
------------------------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message
with 'unsubscribe' in the body to [EMAIL PROTECTED]
