mike wrote: > To me it isn't a memcached vs. session persistency debate. memcached > to me is a cache layer for anything - if I wanted to use it for > sessions, it's an added bonus (I'd probably make sure to use 3.0.0+ so > I could ensure the data is in more than one server, losing people's > session data is a crappy user experience :)) Cache layers are cheap - it's a known science after all. The key thing (AFAICT) about memcached is that is _distributed_. You need this when you don't have session persistency (session being the client-to-server relationship). /Per Jessen, Zürich -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php