Page 1 of 1

session variables - memcache vs. database

Posted: Thu Mar 11, 2010 7:44 am
by mottwsc
I have different operations spread across multiple servers for a LAMP application. I need a way for session data to be accessed across these multiple servers. Using a database table to store session data was the first thought, but then someone suggested using memcache/memcached because it will be cleaner (since it is self-cleaning). I want to use PHP's built-in session handling, but want to direct it elsewhere in terms of where it is stored.

I have two questions:

Is there a strightforward example which shows how to use PHP's built-in session handling but with the use of memcache?

Is there any reason I would use a database table instead of memcache?

Thanks!

Re: session variables - memcache vs. database

Posted: Sat Mar 13, 2010 6:39 pm
by Darhazer
Change settings in your php.ini:

Code: Select all

session.save_handler = memcache
; change server:port to fit your needs...
session.save_path="tcp://server:port?persistent=1&weight=1&timeout=1&retry_interval=15
* found on Google, never used it

Re: session variables - memcache vs. database

Posted: Sat Mar 13, 2010 7:37 pm
by mottwsc
thanks for the suggestion - I'll try that