bad for sessions?
Josh Berkus
josh at agliodbs.com
Fri Feb 11 12:04:32 PST 2005
Perrin,
> i.e. all the data you care about is stored somewhere else in addition to
> memcached. This is a sort of customized version of a write-through
> cache. That sounds like a good plan to me. Blindly replacing a
> database with memcached for sessions is what I think people should
> avoid.
No arguments here. Though I suppose there are some users who don't want
persistent session information ever ...
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
More information about the memcached
mailing list