You can do so much more with storing sessions in a database. For
example, I can determine which of my users is currently on by looking
in the sessions table. Not only does using a database for sessions
offer more security, it also offers more flexibility.
On Jul 22, 2009, at 5:13 AM, Ashley Sheridan wrote:
On Wed, 2009-07-22 at 16:07 +0700, Lenin wrote:
On Wed, Jul 22, 2009 at 2:46 PM, Ashley Sheridan
On Wed, 2009-07-22 at 03:45 +0700, Lenin wrote:
*When you use on-disk files to store session data, those files must
As Floyd suggested keeping your sessions in the DB will give you
session management and security as well.
Why would putting the session data in a database offer more
I'm not meaning to try and poke holes in your idea, I genuinely
know the answer!
*Storing Session Data In A Database
readable and writeable by PHP. On a multi-user hosting system, it is
possible for other users to access your session data through the
(but see the commentary on open_basedir in part 5 of this series.
way to secure your session data is to store it in a database.
I have also studied Zend Certification Study guide by Davey Shafik
Ramsey who said similar things in the book.
And is the database not readable and writeable by PHP? Just seems that
this sort of thing could be properly sorted by the right permissions
level on the file, as I assume you'd be protecting the database in a
similar manner by locking down that to specific users, and determining
what they could and couldn't do.
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php