>> Wouldn't storing the tags in a file for backup solve the problem? You'd >> have to write twice for the tags, but you may have the speed of memcache >> with the reliability of the file storage. >> Of course something like the new ezcCacheStack class as base for such a >> solution would even be better.
I'm considering something like "ezcCacheStack" for the next release after "1.6". IMHO, this _the_ clean way to deal with tags with such backends. And of course this "multi level" cache frontend would have other advantages. Regards -- Fabien MARTY [EMAIL PROTECTED]
