[horde] memcache caching for all session stores..

[liamr at umich.edu]

Hey -

I was looking at CVS and noticed a change last month.  Just want to  
make sure I understand this.

A while ago, there was a memcache+mysql session handler that was deleted..

   http://marc.info/?l=horde-cvs&m=119277817304646&w=2
     It makes no sense to have a DB-backed memcache session handler...

But now, all session handlers can cache session data in memcache.

   http://marc.info/?l=horde-cvs&m=120719156728337&w=2
     Add memcache caching support to all session backends. (Will merge  
to 3.2.1).

I think the new version makes more sense (allowing all session  
handlers to cache data using memcache, rather than creating a memcache  
session handler that used mysql as a secondary store).  I'm just  
curious as to why the new version came into existance?  You still end  
up potentially querying the memcache and DB servers with every page  
load.  It doesn't seem that much different than the original idea  
(tho, it /is/ more flexible)

Liam