hi
Depends a little on what you are doing next.
I am not an htaccess expert so this is written as a 'sessions' user, but if
you use a database/session system you have a lot of flexibility, and can log
what users are up to.
If it is well programmed, with security in mind you can make it very secure
too. Things like lockout after 3 failed logins, site admins without any
authority on the system itself , users with different authorities within the
software etc etc.
On the other hand if you just want a simple restricted area perhaps htaccess
is best
just my 2p worth
Peter
---
Excellence in internet and open source software
---
Sunmaia
www.sunmaia.net
[EMAIL PROTECTED]
tel. 0121-242-1473
---
-Original Message-
From: Brad Hubbard [mailto:[EMAIL PROTECTED]]
Sent: 16 April 2002 02:48
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: [PHP-DB] Definitive answer for large scale
registration/authentication
Can I get some feedback on the conventional wisdom as to the best
solution
for high volume registration and authentication of users
accessing a secure
site? I have worked before with database/session based methods as well as
htaccess. Which is preferred? Are there alternatives?
Thanks for the feedback,
Brad
--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
