RE: [PHP] DATABASE SESSION vs NON DB SESSION
| From: | Jason Cox | Date: | Fri, 13 Oct 2000 14:33:59 +0000 |
| Subject: | RE: [PHP] DATABASE SESSION vs NON DB SESSION | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-20016@lists.php.net to get a copy of this message | ||
Correct. Although I believe server-side session in php don't use cookies,
they propagate the session id through the url with the option of doing it
transparently. I've used DB sessions in the past for two reasons. The
first is that sessions weren't available prior to PHP4 and secondly, you
have a bit more control over what goes on. The server-side sessions are
stored in a directory writable by the server. This is /tmp by default on
Unix/Linux. These session files are readable by anyone with access to the
server.
Jason
-----Original Message-----
From: Jingle Balls [mailto:cgmckeever@norphans.com]
Sent: Friday, October 13, 2000 8:13 AM
To: php-general@lists.php.net
Subject: [PHP] DATABASE SESSION vs NON DB SESSION
I have been reading the posts and some articles about PHP sessions and I got
myself confused (I know it happens a lot). However I am a bit perplexed over
this. I hear a lot of people wanting to keep session information in a DB,
doesnt PHP have a great server side storage of session variables? All you
need to keep client side is a single cookie of the sessionid?
If this is the case, why go the DB route? You can keep preferences and log
info to the actual database, adn read those in when the user logs in and
then keep them as session variables.
Thanks for the input
Chris
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net
For additional commands, e-mail: php-general-help@lists.php.net
To contact the list administrators, e-mail: php-list-admin@lists.php.net
_______________________________________________________
Site Design, Hosting, and E-Commerce at www.webpipe.net