I agree. Using a database is usually a good way of storing session
information. But as noted by Dennis below, automatic logout may require
additional scripts running in the background. This is a bit inferior in
PHP compared to ASP. In ASP, support for automatic session destruction
is implement
On Tue, Jul 16, 2002 at 01:57:51PM -0400, Monty wrote:
> Is there a standard method in PHP for preventing multiple people from using
> the same log-in username/password simultaneously on a membership site? Any
> suggestions are greatly appreciated.
My session management system uses a database bac
lt;[EMAIL PROTECTED]>; "Monty" <[EMAIL PROTECTED]>
Sent: Tuesday, July 16, 2002 3:22 PM
Subject: Re: [PHP] Preventing Multiple Log-Ins after Authentication
> If you do not want to use cookes and use SID or trans SID; Another method
is
> to track your logins via a database. Thi
If you do not want to use cookes and use SID or trans SID; Another method is
to track your logins via a database. This can be resource intensive
though.You need to update the database upon each click or have an empty
window refresh every 1-5 minutes. If there is no activity for 15 or 30
min
You'll have to assign each user a unique id each time they log on. If they
attempt to log on again, check and see if they already have a unique id and
if they do, don't let them log on again.
the problems you'll run into with this is, though, is that if someone
doesn't log out, they'll still have
create cookie and at the end of the Script/page destroy cookies
Use if statements:
setcookie('cookie', $value, $expire, $path
$domain);
if(isset($cookie))
echo "Access Denied, Multiple Login
Attempted!";
[snip]
Is there a standard method in PHP for preventing multiple people from using
the same log-in username/password simultaneously on a membership site? Any
suggestions are greatly appreciated.
[/snip]
One way is to set a non-expiring cookie, which works if they don't delete
cookies from time-to
7 matches
Mail list logo