Lectura de caché de llamadas de retorno
If you want to use 'memcacheD' extention not 'memcache' (there are two diffrent extentions) for session control, you should pay attention to modify php.ini
Most web resource from google is based on memcache because It's earlier version than memcacheD. They will say as following
session.save_handler = memcache
session.save_path = "tcp://localhost:11211"
But it's not valid when it comes to memcacheD
you should modify php.ini like that
session.save_handler = memcached
session.save_path = "localhost:11211"
Look, there is no protocol indentifier
Soporte de sesiones
Memcached proporciona un controlador personalizado de sesiones que puede ser usado para guardar sesiones de usuario en memcache. Utiliza una instancia completamente separada para este propósito, así que se puede usar un grupo de servidores diferente si es necesario. Las claves de sesión son guardadas bajo el prefijo memc.sess.key., hay que tenerlo en cuenta si se utiliza el mismo grupo de servidores para sesiones y caché genérico.
add a note
User Contributed Notes
Soporte de sesiones - [4 notes]
nfoo at naver dot com ¶
2 years ago
Andrei Darashenka ¶
3 years ago
This extension supports Session-locking!
by default
MEMC_SESS_LOCK_ATTEMPTS 30
MEMC_SESS_LOCK_WAIT 100000
MEMC_SESS_LOCK_EXPIRATION 30
taubers at gmail dot com ¶
7 months ago
If you are using the memcache class for session handling your key is the PHP session ID. This is different than when using the memcached class.
Example with memcache:
GET nphu2u8eo5niltfgdbc33ajb62
Example with memcached:
GET memc.sess.key.nphu2u8eo5niltfgdbc33ajb62
For memcached, the prefix is set in the config:
memcached.sess_prefix = "memc.sess.key."
sstratton at php dot net ¶
1 year ago
While the previous poster has a point that Memcached can and will cleanup to make room for it's keys, the likelihood of active sessions (due to the likelihood that they will be written to again within 30 seconds) is fairly low provided you have your memory allocation properly alloted.