Re: Why use sessions and not DB?

The data that is going to get written is only going to be valid for a short time. It is to prevent the user from seeing the same banner more than X times. CDitty At 05:34 PM 8/29/00 , Michael Kimsal wrote:

Agreed. Storing session info into database will let you scale to multiple front end machines much easier. If that's even a remote possibility, you'd want to store info in a db. We've been gzcompressing large amounts of session data (large shopping carts) before writing to the database. Now instead of continually sending receiving 1-2k chunks across the wire between server and db, we send 300-400 bytes each time, which is helping speed things up. Jason Murray wrote:

I am arguing(not really) with one of my partners about the use of

sessions. He

is new to web programming but has been programming other db related

languages

for years. He wants to use the db to store certain information and I

want to

use sessions.

Why not store the session info in a database? Jason (setting cats amongst pigeons ;)) -- Jason Murray jasonm@melbourneit.com.au Web Design Team, Melbourne IT Don't believe everything you're foretold. -- 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 -- ========================== Michael Kimsal http://www.tapinternet.com 734-480-9961 -- 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